From: Tim Deegan <tim@xen.org>
To: George Dunlap <george.dunlap@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xen: Make sure log-dirty is turned off before trying to dismantle it
Date: Thu, 8 Mar 2012 12:33:28 +0000 [thread overview]
Message-ID: <20120308123328.GF64337@ocelot.phlegethon.org> (raw)
In-Reply-To: <1331209562.32288.47.camel@elijah>
At 12:26 +0000 on 08 Mar (1331209562), George Dunlap wrote:
> On Thu, 2012-03-08 at 12:17 +0000, Tim Deegan wrote:
> > At 17:58 +0000 on 07 Mar (1331143125), George Dunlap wrote:
> > > diff --git a/xen/arch/x86/mm/paging.c b/xen/arch/x86/mm/paging.c
> > > --- a/xen/arch/x86/mm/paging.c
> > > +++ b/xen/arch/x86/mm/paging.c
> > > @@ -722,6 +722,10 @@ int paging_domctl(struct domain *d, xen_
> > > /* Call when destroying a domain */
> > > void paging_teardown(struct domain *d)
> > > {
> > > + /* Make sure log-dirty is turned off before trying to dismantle it.
> > > + * Needs to be done here becuse it's covered by the hap/shadow lock */
> > > + d->arch.paging.log_dirty.disable_log_dirty(d);
> > > +
> > > if ( hap_enabled(d) )
> > > hap_teardown(d);
> > > else
> > >
> >
> > This isn't needed upstream because the spinlock confusion that it's
> > papering over has been properly fixed (by eliminating the log-dirty
> > lock).
>
> Yes; I'm afraid I didn't read the ticket referenced here very well
> either. Sorry about that -- it just looked so obvious. :-)
>
> It looks like Keir has already added it -- do you want to revert it?
Yep - though I see it's already been reverted too. :) The code is
harmless enough but the comment was confusing.
Tim.
prev parent reply other threads:[~2012-03-08 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 17:58 [PATCH] xen: Make sure log-dirty is turned off before trying to dismantle it George Dunlap
2012-03-08 12:17 ` Tim Deegan
2012-03-08 12:26 ` George Dunlap
2012-03-08 12:30 ` Keir Fraser
2012-03-08 12:33 ` Tim Deegan [this message]
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=20120308123328.GF64337@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=george.dunlap@citrix.com \
--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.