public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>
To: "kraxel@redhat.com" <kraxel@redhat.com>,
	"Xu, Min M" <min.m.xu@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: EFI shell with microvm
Date: Mon, 10 Jan 2022 09:05:41 +0000	[thread overview]
Message-ID: <26f59d36171a8465d318af8b34410e770fdd2615.camel@intel.com> (raw)
In-Reply-To: <PH0PR11MB50644277713218D0D58CD9C0C5509@PH0PR11MB5064.namprd11.prod.outlook.com>

On Mon, 2022-01-10 at 00:16 +0000, Xu, Min M wrote:
> 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

Oh I see, that's great actually because as I mentioned earlier this is
not Xen specific, therefore I really think the renaming you're doing is
important.

> > 
> Thanks
> Min

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

  reply	other threads:[~2022-01-10  9:05 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
2022-01-10  9:05             ` Boeuf, Sebastien [this message]
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=26f59d36171a8465d318af8b34410e770fdd2615.camel@intel.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