* [PATCH] xen: Make sure log-dirty is turned off before trying to dismantle it
@ 2012-03-07 17:58 George Dunlap
2012-03-08 12:17 ` Tim Deegan
0 siblings, 1 reply; 5+ messages in thread
From: George Dunlap @ 2012-03-07 17:58 UTC (permalink / raw)
To: xen-devel; +Cc: george.dunlap
Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] xen: Make sure log-dirty is turned off before trying to dismantle it
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
0 siblings, 1 reply; 5+ messages in thread
From: Tim Deegan @ 2012-03-08 12:17 UTC (permalink / raw)
To: George Dunlap; +Cc: xen-devel
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).
Cheers,
Tim.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] xen: Make sure log-dirty is turned off before trying to dismantle it
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
0 siblings, 2 replies; 5+ messages in thread
From: George Dunlap @ 2012-03-08 12:26 UTC (permalink / raw)
To: Tim Deegan; +Cc: George Dunlap, xen-devel@lists.xensource.com
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?
-George
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] xen: Make sure log-dirty is turned off before trying to dismantle it
2012-03-08 12:26 ` George Dunlap
@ 2012-03-08 12:30 ` Keir Fraser
2012-03-08 12:33 ` Tim Deegan
1 sibling, 0 replies; 5+ messages in thread
From: Keir Fraser @ 2012-03-08 12:30 UTC (permalink / raw)
To: George Dunlap, Tim Deegan; +Cc: xen-devel@lists.xensource.com
On 08/03/2012 12:26, "George Dunlap" <george.dunlap@citrix.com> 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?
Done.
-- Keir
> -George
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] xen: Make sure log-dirty is turned off before trying to dismantle it
2012-03-08 12:26 ` George Dunlap
2012-03-08 12:30 ` Keir Fraser
@ 2012-03-08 12:33 ` Tim Deegan
1 sibling, 0 replies; 5+ messages in thread
From: Tim Deegan @ 2012-03-08 12:33 UTC (permalink / raw)
To: George Dunlap; +Cc: George Dunlap, xen-devel@lists.xensource.com
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2012-03-08 12:33 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.