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: Re: [PATCH]Add a flag for shadow pages
Date: Wed, 04 Mar 2009 16:32:11 +0000 [thread overview]
Message-ID: <49AEAD0B.7040301@eu.citrix.com> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098401C7C9DEA9@PDSMSX501.ccr.corp.intel.com>
Jiang, Yunhong wrote:
> Thanks for your really quick-hand implementation. I will update my another patch accordingly tomorrow.
>
> So still one question to the two assertion (or to Tim??) in sh_rm_write_access_from_sl1p()/sh_put_ref(). What's the potential error to be protected by this checking? If page is a shadow, it's count_info will always be 0, right? Or it is just a sanity checking?
They're sanity checking. Checks are there to be sure that the page is a
shadow page. It used to be "->mbz == 0", which was clearer, in the old
page_info model.
In the sh_rm_write_access_from_sl1p(), the check is there to ensure that
the page is *still* a shadow page. As for current code, though, that
check should be useless.
I actually think that having a more precise way of knowing when a page
is a shadow page is definitely needed, for debugging or even in case the
shadow allocation becomes more dynamic in the future.
> I need change this is because, if we mark a page offline, then the count_info is not 0, even for shadow page. Can I just checking the count_mask here?
Ehr, I am not following the discussions about your patch, but I suppose
you set the page off-line after all references and uses of the page,
even inside shadows, are removed. Or the count_info is != 0 to signal
that the page is going offline?
Thanks,
Gianluca
next prev parent reply other threads:[~2009-03-04 16:32 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
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 [this message]
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=49AEAD0B.7040301@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.