All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gianluca Guida <gianluca.guida@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>
Cc: Tim Deegan <Tim.Deegan@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH] Do not set page's count_info directly
Date: Thu, 05 Mar 2009 15:21:27 +0000	[thread overview]
Message-ID: <49AFEDF7.10709@eu.citrix.com> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098401C7CE8F02@PDSMSX501.ccr.corp.intel.com>



Jiang, Yunhong wrote:
> Keir Fraser <mailto:keir.fraser@eu.citrix.com> wrote:
>> On 05/03/2009 12:45, "Gianluca Guida" <glguida@gmail.com> wrote:
>>
>>> On Thu, Mar 5, 2009 at 1:38 PM, Tim Deegan
>> <Tim.Deegan@citrix.com> wrote:
>>>> The check doesn't tell you it's a shadow page -- it just tells you it's
>>>> *not* allocated in another way.  Checking with the mask is OK here,
>>>> perhaps with a comment change.
>>> Yes, but this is what the code (in the shadow code) intends to check.
>>> My complete plan is to have this macro and restore the idea of having
>>> a flag for shadow pages because, as for now, the fact that we can't
>>> distinguish clearly a shadow page should be considered a sort of bug,
>>> given the code assumptions. Or at least a good basis for future bugs.
>> I'm happy for shadow code to have another bit in count_info
>> for its own use.
>> I don't think it's good to have other code (e.g., generic page offlining
>> code) peeking at it, is all. The particular case for a new
>> flag described
>> above sounds fine.
> 
> The new code is not using that flag anymore, it is use the page_get_owner_and_reference() to get the owner.

Yes, I was actually thinking about adding it. Turns out that I realized 
that it's not the best way to do stuff, but I think that I'll do the 
following:

- add a sh_page_is_a_shadow_page() in shadow code to make the code less 
confusing (with a small caveat comment about not being perfectly precise).
- exercise my English skills by writing a comment in page_info that 
summarizes this thread findings about current use if count_info and 
shadow pages.

Thanks,
Gianluca

  reply	other threads:[~2009-03-05 15:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05  9:11 [PATCH] Do not set page's count_info directly Jiang, Yunhong
2009-03-05 12:32 ` Gianluca Guida
2009-03-05 12:38   ` Tim Deegan
2009-03-05 12:45     ` Gianluca Guida
2009-03-05 13:20       ` Keir Fraser
2009-03-05 14:34         ` Jiang, Yunhong
2009-03-05 15:21           ` Gianluca Guida [this message]
2009-03-06  3:14             ` Jiang, Yunhong
2009-03-05 12:45   ` Keir Fraser
2009-03-05 14:33     ` Jiang, Yunhong
2009-03-05 14:50       ` Keir Fraser
2009-03-05 15:07         ` Jiang, Yunhong
2009-03-05 14:45   ` Jiang, Yunhong

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=49AFEDF7.10709@eu.citrix.com \
    --to=gianluca.guida@eu.citrix.com \
    --cc=Keir.Fraser@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.