From: Olaf Hering <olaf@aepfle.de>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: Keir Fraser <keir.xen@gmail.com>,
Paul Durrant <Paul.Durrant@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
James Harper <james.harper@bendigoit.com.au>
Subject: Re: map memory holes with same page
Date: Mon, 23 May 2011 13:03:34 +0200 [thread overview]
Message-ID: <20110523110334.GA21810@aepfle.de> (raw)
In-Reply-To: <20110523091307.GC12250@whitby.uk.xensource.com>
On Mon, May 23, Tim Deegan wrote:
> At 09:42 +0100 on 23 May (1306143771), Paul Durrant wrote:
> > > -----Original Message-----
> > [snip]
> > >
> > > Should there be a performance impact if Windows tries to touch a
> > > page that I have previously given pack with decrease_reservation?
> > > Will that invoke the PoD sweep?
> > >
> >
> > No. The p2m entry will be 'invalid', not 'PoD'. IIRC the sweep should
> > only be invoked if the cache is exhausted when trying to fix up a PoD
> > entry.
>
> But yes, there will be a performance impact because all accesses to the
> missing page will be emulated by sending an ioreq to qemu, so it will
> run _very_ slowly.
Isnt that what I just "fixed" for kdump, the new get_mem_type hvmop?
Could that be reused for this Windows issue?
Olaf
next prev parent reply other threads:[~2011-05-23 11:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 9:41 map memory holes with same page James Harper
2011-05-21 10:14 ` Keir Fraser
2011-05-21 10:17 ` James Harper
2011-05-23 8:30 ` Tim Deegan
2011-05-23 8:42 ` Paul Durrant
2011-05-23 9:13 ` Tim Deegan
2011-05-23 9:23 ` Paul Durrant
2011-05-23 10:29 ` James Harper
2011-05-23 10:37 ` Tim Deegan
2011-05-23 11:06 ` James Harper
2011-05-23 11:03 ` Olaf Hering [this message]
2011-05-23 12:01 ` Tim Deegan
2011-05-23 12:51 ` James Harper
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=20110523110334.GA21810@aepfle.de \
--to=olaf@aepfle.de \
--cc=Paul.Durrant@citrix.com \
--cc=Tim.Deegan@citrix.com \
--cc=james.harper@bendigoit.com.au \
--cc=keir.xen@gmail.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.