From: David Woodhouse <dwmw2@infradead.org>
To: "Ni, Ray" <ray.ni@intel.com>, Gerd Hoffmann <kraxel@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
"Richardson, Brian" <brian.richardson@intel.com>
Cc: "Justen, Jordan L" <jordan.l.justen@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Kevin O'Connor <kevin@koconnor.net>,
Anthony Perard <anthony.perard@citrix.com>
Subject: Re: Drop CSM support in OvmfPkg?
Date: Tue, 22 Jan 2019 16:23:06 +0000 [thread overview]
Message-ID: <e1ecedc8dea690aa9e29fc4409702a6d82bbd568.camel@infradead.org> (raw)
In-Reply-To: <734D49CCEBEEF84792F5B80ED585239D5BFCEBF2@SHSMSX103.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
On Tue, 2019-01-22 at 16:13 +0000, Ni, Ray wrote:
> David,
> I'd like to re-start the discussion.
> Could you please kindly explain the background/reason of adding CSM
> support in OVMF?
> Maybe knowing the reason can help to make further decisions of
> whether to
> A. keep it outside OvmfPkg
> B. keep it inside OvmfPkg
> C. maybe have a chance to just remove the CSM support after
> revisiting
The idea was to make it simple to have a single firmware image for
virtual machines which would support both UEFI and Legacy boot for
guests simultaneously.
In libvirt there has been an alternative approach, where the BIOS image
is switched between OVMF and SeaBIOS according to the configuration of
the guest VM.
That's fine for libvirt, but in situations where VM hosting is provided
as a service, it becomes quite painful to manage the 'UEFI' vs.
'Legacy' flags on guest images and then switch firmware images
accordingly. A one-size-fits-all BIOS using OVMF+CSM is very much
preferable.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2019-01-22 16:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 2:23 Drop CSM support in OvmfPkg? Ni, Ruiyu
2018-12-17 9:54 ` Laszlo Ersek
2018-12-17 10:44 ` Ni, Ruiyu
2018-12-20 6:44 ` Gerd Hoffmann
2018-12-20 13:37 ` David Woodhouse
2018-12-20 14:55 ` Ni, Ruiyu
2019-01-22 16:13 ` Ni, Ray
2019-01-22 16:23 ` David Woodhouse [this message]
2019-01-23 3:43 ` Ni, Ray
2019-01-23 4:00 ` Andrew Fish
2019-01-23 4:29 ` Ni, Ray
2019-01-23 9:46 ` Laszlo Ersek
2019-01-23 9:49 ` David Woodhouse
2019-01-24 1:48 ` Ni, Ray
2019-01-24 9:31 ` David Woodhouse
2019-01-24 11:30 ` Laszlo Ersek
2019-01-25 20:28 ` Brian J. Johnson
2019-01-28 8:23 ` Laszlo Ersek
2019-01-23 12:26 ` Ard Biesheuvel
2019-01-23 6:12 ` Gerd Hoffmann
2019-01-23 8:42 ` David Woodhouse
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=e1ecedc8dea690aa9e29fc4409702a6d82bbd568.camel@infradead.org \
--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