All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Tim Deegan <Tim.Deegan@citrix.com>
Subject: Re: query the page type of a hvm page from within a hvm guest
Date: Mon, 2 May 2011 11:56:48 +0200	[thread overview]
Message-ID: <20110502095648.GB21248@aepfle.de> (raw)
In-Reply-To: <4DBE98FF020000780003F22F@vpn.id2.novell.com>

On Mon, May 02, Jan Beulich wrote:

> > +	if (get_mem_type_supported)
> 
> The name of the variable seems badly chosen, and the way you
> coded this the code wouldn't be able to use the new interface
> after migrating from an incapable hypervisor to a capable one.

For the plain kdump usage thats probably ok. I think ballooned out
oldmem pages will turn into ram pages during migration, but I'm not sure.

> > +		return -ENXIO;
> > +
> > +	if (pfn == prev_pfn)
> > +		return prev_mem_type == HVMMEM_ram_rw;
> 
> Did you in fact observe many immediately subsequent calls with
> the same input (i.e. is the caching really worthwhile)?

It depends on how expensive a hypercall is.
read_from_oldmem() did read full pages in my testing.
I think removing the caching and do the hypercall unconditional is ok.

Olaf

  reply	other threads:[~2011-05-02  9:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07 10:12 query the page type of a hvm page from within a hvm guest Olaf Hering
2011-04-07 11:16 ` Tim Deegan
2011-05-02  9:17   ` Olaf Hering
2011-05-02  9:43     ` Jan Beulich
2011-05-02  9:56       ` Olaf Hering [this message]
2011-05-02 16:27       ` Olaf Hering
2011-05-03  7:49         ` Jan Beulich

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=20110502095648.GB21248@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=JBeulich@novell.com \
    --cc=Tim.Deegan@citrix.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.