From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2] pc: allow raising low memory via max-ram-below-4g option
Date: Sun, 24 Jan 2016 08:37:12 +0200 [thread overview]
Message-ID: <20160124083526-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1453459914.17005.16.camel@redhat.com>
On Fri, Jan 22, 2016 at 11:51:54AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > > > I wonder whether we should just bite the bullet and ask management to
> > > > maintain the physical memory map for us, instead of trying to give us
> > > > hints.
> > >
> > > I doubt this simplified things, given the backward compatibility
> > > constrains we have.
> > >
> > > cheers,
> > > Gerd
> >
> > That's exactly what would become simple.
> > For backwards compatibility we would leave things alone
> > if the new flags for the memory map aren't specified.
>
> But we'll add a bunch of new code for the new config mode which allows
> management to maintain the physical memory map. And we'll expect
> management know about a bunch of machine type internals.
Yes we don't want that. I was vaguely thinking some kind
of query that reports the required info so management
just has to maintain that.
> That isn't a
> simplification.
>
> > This would allow people to e.g. allocate phy address
> > ranges for things like nvdimm which has been
> > problematic in the past.
>
> Didn't follow nvdimm discussions. If you think we really need that
> anyway to solve certain issues, sure, go ahead and I happily adjust this
> patch to use the new infrastructure.
>
> cheers,
> Gerd
I'd like to gather some feedback from management folk first.
--
MST
next prev parent reply other threads:[~2016-01-24 6:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 12:58 [Qemu-devel] [PATCH v2] pc: allow raising low memory via max-ram-below-4g option Gerd Hoffmann
2016-01-08 17:45 ` Igor Mammedov
2016-01-08 18:32 ` Laszlo Ersek
2016-01-11 8:26 ` Gerd Hoffmann
2016-01-11 12:16 ` Laszlo Ersek
2016-01-11 12:26 ` Marcel Apfelbaum
2016-01-14 23:45 ` Eric Blake
2016-01-19 12:37 ` Eduardo Habkost
2016-01-20 14:55 ` Gerd Hoffmann
2016-01-20 15:34 ` Eduardo Habkost
2016-01-20 17:15 ` Eduardo Habkost
2016-01-20 17:25 ` Michael S. Tsirkin
2016-01-21 7:48 ` Gerd Hoffmann
2016-01-21 9:37 ` Michael S. Tsirkin
2016-01-22 10:51 ` Gerd Hoffmann
2016-01-24 6:37 ` Michael S. Tsirkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-02 8:48 Gerd Hoffmann
2015-11-03 10:06 Gerd Hoffmann
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=20160124083526-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.