From: "Min Xu" <min.m.xu@intel.com>
To: "kraxel@redhat.com" <kraxel@redhat.com>,
"Boeuf, Sebastien" <sebastien.boeuf@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: EFI shell with microvm
Date: Mon, 10 Jan 2022 00:16:09 +0000 [thread overview]
Message-ID: <PH0PR11MB50644277713218D0D58CD9C0C5509@PH0PR11MB5064.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220107133727.gky4tmrhe7rchtfb@sirius.home.kraxel.org>
On January 7, 2022 9:37 PM, Gerd Hoffmann wrote:
>
> > > tianocore doesn't use interrupts (other than timer).
> >
> > Yes I realized that by diving into the code. I can see microvm using
> > the Xen timer while OvmfPkgX64 uses 8254 PIT.
>
> Min, what happened to the patch series changing that?
Hi Gerd, What do you mean "the patch series"? Is this one? https://edk2.groups.io/g/devel/message/83488
It is still in review and hasn't been merged.
>
> (the plan is to always use the lapci except when compiling with csm enabled
> because pit/pic support is needed for backward compatibility reasons then).
Yes, we use CSM_ENABLE to switch the lapic timer or 8254 timer in build time.
This is the v3 which has been reviewed. https://github.com/tianocore/edk2/pull/2167
>
Thanks
Min
next prev parent reply other threads:[~2022-01-10 0:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 11:25 EFI shell with microvm Boeuf, Sebastien
2022-01-06 12:44 ` Gerd Hoffmann
2022-01-06 13:08 ` Boeuf, Sebastien
2022-01-07 12:07 ` Gerd Hoffmann
2022-01-07 13:06 ` Boeuf, Sebastien
2022-01-07 13:37 ` Gerd Hoffmann
2022-01-10 0:16 ` Min Xu [this message]
2022-01-10 9:05 ` Boeuf, Sebastien
2022-01-07 14:12 ` Boeuf, Sebastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PH0PR11MB50644277713218D0D58CD9C0C5509@PH0PR11MB5064.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox