From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Michal Novotny <minovotn@redhat.com>,
"'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Disallow setting maxmem to higher value than total physical memory size
Date: Thu, 2 Sep 2010 06:43:20 +0100 [thread overview]
Message-ID: <1283406200.3469.143.camel@localhost.localdomain> (raw)
In-Reply-To: <4C7EC13D.2040905@goop.org>
On Wed, 2010-09-01 at 22:10 +0100, Jeremy Fitzhardinge wrote:
>
> > It's not only in xenstore, it is also in the result of the
> > XENMEM_get_memory_map hypercall.
>
> Is that separate from 3?
As far as the h/v is concerned yes. Although they know it's an e820 the
set/get_memory_map hypercalls basically store an opaque blob so far as
the h/v is concerned. xend doesn't seem so sure they are unrelated...
> > Old-style PV Linux domains really do use static-max in this way. It may
> > well be that there are potentially better ways for guests to implement
> > this in the future but we have a deployed base of guests which work this
> > way.
>
> I specifically meant the Xenstore "static-max" value is useless.
> Getting it via hypercall is fine.
I'm not sure but I think this is used by HVM balloon drivers when PoD is
active. I don't know why this is the case though, other than
XENMEM_get_memory_map being a PV only hypercall.
Ian.
prev parent reply other threads:[~2010-09-02 5:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 12:31 [PATCH] Disallow setting maxmem to higher value than total physical memory size Michal Novotny
2010-09-01 12:44 ` Ian Campbell
2010-09-01 13:01 ` Michal Novotny
2010-09-01 13:37 ` Ian Campbell
2010-09-01 14:18 ` Michal Novotny
2010-09-01 14:21 ` Michal Novotny
2010-09-01 14:26 ` Jan Beulich
2010-09-01 14:50 ` Michal Novotny
2010-09-01 15:00 ` Jan Beulich
2010-09-01 15:10 ` Michal Novotny
2010-09-01 15:14 ` Jan Beulich
2010-09-01 15:20 ` Ian Campbell
2010-09-01 15:34 ` Michal Novotny
2010-09-01 16:53 ` Jeremy Fitzhardinge
2010-09-01 17:56 ` Ian Campbell
2010-09-01 18:15 ` Jeremy Fitzhardinge
2010-09-01 18:53 ` Ian Campbell
2010-09-01 21:10 ` Jeremy Fitzhardinge
2010-09-02 5:43 ` Ian Campbell [this message]
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=1283406200.3469.143.camel@localhost.localdomain \
--to=ian.campbell@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=minovotn@redhat.com \
--cc=xen-devel@lists.xensource.com \
/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.