qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ani Sinha <ani@anisinha.ca>
To: Gerd Hoffmann <kraxel@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Igor Mammedov <imammedo@redhat.com>
Subject: Re: any opinion on the patch "[RFC PATCH] hw/i386/e820: remove legacy reserved entries for e820"? EOM
Date: Fri, 4 Mar 2022 16:16:38 +0530	[thread overview]
Message-ID: <CAARzgwximWns6yiWhTUogPjNVN3iGOPfs4z_i5BR2DLTH4ancg@mail.gmail.com> (raw)
In-Reply-To: <CAARzgwy33DZwoXzMMYCd1e4-88hyzChX-VpHH65P71PW6Ko4Ng@mail.gmail.com>

On Fri, Mar 4, 2022 at 4:11 PM Ani Sinha <ani@anisinha.ca> wrote:
>
> On Fri, Mar 4, 2022 at 3:48 PM Gerd Hoffmann <kraxel@redhat.com> wrote:
> >
> > On Thu, Mar 03, 2022 at 03:12:51PM +0530, Ani Sinha wrote:
> > > On Thu, Mar 3, 2022 at 15:11 Gerd Hoffmann <kraxel@redhat.com> wrote:
> > >
> > > > Sorry, no.  Noticed the discussions but don't remember the details and
> > > > didn't took the time to wade through the code to refresh my memory.
> > >
> > > Could you please take a look when you get time? You have the most context
> > > in this space I believe.
> >
> > Should indeed not be needed unless you use a stone-aged seabios version.
> > But I think you can't simply drop it for live migration compatibility
> > reasons.  So you'll need do the compatibility dance and drop it for new
> > machine types only.  I doubt the benefits outweigh that effort ..
>
> Igor what do you think?
Since the static entries are separate from the rom file entries, I
think we are in trouble only if the destination is using an old bios?
Otherwise, the non-existence of the static entries should be simply
ignored right?


  reply	other threads:[~2022-03-04 10:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAARzgwyjqEs96QXthDs_yQi_s7qmMsLuH+4YQcq2Hx01_vY3EA@mail.gmail.com>
     [not found] ` <20220303094134.tuhhrvtstxwpksmh@sirius.home.kraxel.org>
     [not found]   ` <CAARzgwxFuY=xMQmHU0cocG3ecznhVwQVTF0naaA6wwFkhwvOyA@mail.gmail.com>
     [not found]     ` <20220304101846.ct3ge56w6gjq355o@sirius.home.kraxel.org>
2022-03-04 10:41       ` any opinion on the patch "[RFC PATCH] hw/i386/e820: remove legacy reserved entries for e820"? EOM Ani Sinha
2022-03-04 10:46         ` Ani Sinha [this message]
2022-03-10 16:26           ` Igor Mammedov

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-all 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=CAARzgwximWns6yiWhTUogPjNVN3iGOPfs4z_i5BR2DLTH4ancg@mail.gmail.com \
    --to=ani@anisinha.ca \
    --cc=imammedo@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).