All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
	Tim Deegan <Tim.Deegan@eu.citrix.com>,
	Gianluca Guida <Gianluca.Guida@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH]Add a flag for shadow pages
Date: Wed, 04 Mar 2009 11:57:15 +0000	[thread overview]
Message-ID: <C5D41D1B.3BD5%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C5D400CD.4168%keir.fraser@eu.citrix.com>

On 04/03/2009 09:56, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:

> Another would be to create a new function page_get_reference_and_owner()
> which obtains a reference on a guest page and *returns* the (now known
> valid) domain pointer. Probably this is nicer actually. Then all existing
> users of page_get_owner() need checking to ensure they don't need to use the
> new more expensive function -- I think some are probably actually unsafe now
> that shadow pages clobber the domain field.

I'm working on this by the way. I'll clean up everything except shadow uses
of page_get_owner(). The only two possibly suspect uses I can see (most are
just ASSERT/BUG_ON uses I think are okay):
 * sh_mfn_is_a_pagetable()
 * shadow_get_page_from_l1e()

It'd be good if Tim or Gianluca would check whether these need to be more
careful -- could page_get_owner() return a duff non-NULL value in either of
these functions? This could only happen if the pages they work on could
possibly actually be shadow pages with clobbered page owner field.

 -- Keir

  reply	other threads:[~2009-03-04 11:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04  8:46 [PATCH]Add a flag for shadow pages Jiang, Yunhong
2009-03-04  9:06 ` Keir Fraser
2009-03-04  9:17   ` Jiang, Yunhong
2009-03-04  9:22     ` Keir Fraser
2009-03-04  9:28       ` Jiang, Yunhong
2009-03-04  9:56         ` Keir Fraser
2009-03-04 11:57           ` Keir Fraser [this message]
2009-03-04 12:13             ` Tim Deegan
2009-03-04 13:19               ` Keir Fraser
2009-03-04 14:30             ` Keir Fraser
2009-03-04 16:01               ` Jiang, Yunhong
2009-03-04 16:32                 ` Gianluca Guida
2009-03-05  2:41                   ` Jiang, Yunhong
2009-03-04 16:45                 ` Keir Fraser
2009-03-04  9:20 ` Keir Fraser

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=C5D41D1B.3BD5%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Gianluca.Guida@eu.citrix.com \
    --cc=Tim.Deegan@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.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.