qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: pbonzini@redhat.com, "Michael S. Tsirkin" <mst@redhat.com>,
	afaerber@suse.de, aliguori@amazon.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2 v2] pc: inform SeaBIOS where 64-bit PCI hole begins
Date: Mon, 4 Nov 2013 15:35:15 +0100	[thread overview]
Message-ID: <20131104153515.0a5b9c32@nial.usersys.redhat.com> (raw)
In-Reply-To: <1383569283.8610.36.camel@nilsson.home.kraxel.org>

On Mon, 04 Nov 2013 13:48:03 +0100
Gerd Hoffmann <kraxel@redhat.com> wrote:

>   Hi,
> 
> > > So maybe design that with memory hotplug in mind?  Such as adding a new
> > > qemu-specific type QEMU_RAM_HOTPLUG?  Which seabios could use to reserve
> > > the memory (but not add it to the e820 table for the guest)?
> > It will do job too. But extending semantics of standard table would be
> > confusing. Yes, Seabios will filter it out but it doesn't make table
> > less confusing.
> 
> Was just thinking that it might be easier that way if we need e820
> entries for hotplug memory address space _anyway_.
I don't think that we need e820 entries for hotplug memory reserved space as
e820 should. In case present at boot hotpluggable DIMMs would be needed in E820,
we can add them as usual E820_RAM entries.

But regardless of what we do here it might be good keep option of adding non
standard entries in future, by filtering out unknown types in SeaBIOS.

> 
> > I'd prefer having a dedicated interface for it as a more clean solution.
> 
> Agree.

So back to naming question, would you agree to renaming fw_cfg to the last
Michael's suggestion "reserved-memory-end"?
 
> cheers,
>   Gerd
> 
> 
> 

  reply	other threads:[~2013-11-04 14:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 12:57 [Qemu-devel] [PATCH 0/2 v2] pc: inform SeaBIOS where 64-bit PCI hole begins Igor Mammedov
2013-10-29 12:57 ` [Qemu-devel] [PATCH 1/2] pc: map PCI address space as catchall region for not mapped addresses Igor Mammedov
2013-10-29 12:57 ` [Qemu-devel] [PATCH 2/2] pc: add 'etc/pcimem64-minimum-address' fw_cfg interface to SeaBIOS Igor Mammedov
2013-10-29 15:10 ` [Qemu-devel] [PATCH 0/2 v2] pc: inform SeaBIOS where 64-bit PCI hole begins Michael S. Tsirkin
2013-10-29 15:28   ` Igor Mammedov
2013-10-29 18:52     ` Michael S. Tsirkin
2013-10-30 12:57       ` Gerd Hoffmann
2013-10-30 13:24       ` Igor Mammedov
2013-10-30 13:48         ` Michael S. Tsirkin
2013-10-30 14:33           ` Gerd Hoffmann
2013-10-30 15:38             ` Igor Mammedov
2013-11-04 12:48               ` Gerd Hoffmann
2013-11-04 14:35                 ` Igor Mammedov [this message]
2013-11-04 15:18                   ` Gerd Hoffmann
2013-10-30 13:29       ` 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=20131104153515.0a5b9c32@nial.usersys.redhat.com \
    --to=imammedo@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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).