From: Olaf Hering <olaf@aepfle.de>
To: Tim Deegan <tim@xen.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] xenpaging: check p2mt in p2m_mem_paging functions
Date: Thu, 13 Oct 2011 14:14:02 +0200 [thread overview]
Message-ID: <20111013121402.GA20431@aepfle.de> (raw)
In-Reply-To: <20111013112755.GE44937@ocelot.phlegethon.org>
On Thu, Oct 13, Tim Deegan wrote:
> Hi,
>
> At 14:42 +0200 on 11 Oct (1318344151), Olaf Hering wrote:
> > @@ -897,9 +903,16 @@ void p2m_mem_paging_resume(struct domain
> > {
> > p2m_lock(p2m);
> > mfn = p2m->get_entry(p2m, rsp.gfn, &p2mt, &a, p2m_query, NULL);
> > - set_p2m_entry(p2m, rsp.gfn, mfn, 0, p2m_ram_rw, a);
> > - set_gpfn_from_mfn(mfn_x(mfn), rsp.gfn);
> > - audit_p2m(p2m, 1);
> > + /* Allow only pages which were prepared properly or pages which were nominated but not evicted */
> > + if ( mfn_valid(mfn) && ( p2mt == p2m_ram_paging_in || p2mt == p2m_ram_paging_in_start ) )
>
> Wouldn't a nominated-but-not-evicted page have type p2m_ram_paging_out?
Yes, but in the page-in path it will be p2m_ram_paging_in_start with a
valid mfn.
> > + {
> > + set_p2m_entry(p2m, rsp.gfn, mfn, 0, p2m_ram_rw, a);
> > + set_gpfn_from_mfn(mfn_x(mfn), rsp.gfn);
> > + audit_p2m(p2m, 1);
> > + /* May be called more than once if the gfn was populate from different vcpus */
> > + } else if ( p2mt != p2m_ram_rw ) {
> > + printk("resume: %d %lx %x %lx\n", d->domain_id, rsp.gfn, p2mt, mfn_x(mfn));
>
> This should be a gdprintk of some kind, probably XENLOG_WARNING unless
> it happens a lot.
Its just debug, perhaps that gfn was already use for something else
while the pager processed multiple page-in requests from different
vcpus.
Do you want me to resend this patch?
Olaf
next prev parent reply other threads:[~2011-10-13 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 12:42 [PATCH] xenpaging: check p2mt in p2m_mem_paging functions Olaf Hering
2011-10-13 11:27 ` Tim Deegan
2011-10-13 12:14 ` Olaf Hering [this message]
2011-10-13 14:27 ` Tim Deegan
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=20111013121402.GA20431@aepfle.de \
--to=olaf@aepfle.de \
--cc=tim@xen.org \
--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.