From: Tim Deegan <tim@xen.org>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: [RFC PATCH 12/16]: PVH xen: return PVH features during creation, etc...
Date: Thu, 24 Jan 2013 16:57:19 +0000 [thread overview]
Message-ID: <20130124165719.GL20551@ocelot.phlegethon.org> (raw)
In-Reply-To: <20130111180736.36c662d6@mantra.us.oracle.com>
At 18:07 -0800 on 11 Jan (1357927656), Mukesh Rathor wrote:
> Debug.c: we don't need to lock the page, as no path it's called from
> requires that.
I'm afraid it does need to lock it: it's going to write to the page, so
it can't risk having the page freed underfoot.
Tim.
next prev parent reply other threads:[~2013-01-24 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 2:07 [RFC PATCH 12/16]: PVH xen: return PVH features during creation, etc Mukesh Rathor
2013-01-14 12:20 ` Jan Beulich
2013-01-17 23:36 ` Mukesh Rathor
2013-01-18 2:29 ` Mukesh Rathor
2013-01-18 9:23 ` Jan Beulich
2013-01-18 20:41 ` Mukesh Rathor
2013-01-24 16:57 ` Tim Deegan [this message]
2013-01-25 2:08 ` Mukesh Rathor
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=20130124165719.GL20551@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Xen-devel@lists.xensource.com \
--cc=mukesh.rathor@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).