From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Bugfix for VMI paravirt ops
Date: Thu, 05 Apr 2007 18:42:17 -0700 [thread overview]
Message-ID: <4615A579.10103@vmware.com> (raw)
In-Reply-To: <4615A431.5040104@goop.org>
Jeremy Fitzhardinge wrote:
> Zachary Amsden wrote:
>
>> Do you mean kmap_atomic_pfn?
>>
>
> Yes.
>
>
>> kunmap_atomic can stay lazy (at least for VMI), actually, but it
>> doesn't help since it happens outside the spin lock.
>>
>
> May as well be consistent. Or do you mean you can't flush outside the
> spinlock, even if there's nothing pending?
>
Consistency is good. Flush is always fine, just an extra function call.
Zach
next prev parent reply other threads:[~2007-04-06 1:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 23:29 [PATCH] Bugfix for VMI paravirt ops Zachary Amsden
2007-04-05 23:34 ` Zachary Amsden
2007-04-05 23:55 ` Andrew Morton
2007-04-05 23:54 ` Andi Kleen
2007-04-06 0:01 ` Zachary Amsden
2007-04-06 0:08 ` Jeremy Fitzhardinge
2007-04-06 0:09 ` Zachary Amsden
2007-04-06 0:14 ` Jeremy Fitzhardinge
2007-04-06 0:20 ` Zachary Amsden
2007-04-06 0:33 ` Jeremy Fitzhardinge
2007-04-06 0:45 ` Zachary Amsden
2007-04-06 0:52 ` Jeremy Fitzhardinge
2007-04-06 0:54 ` Zachary Amsden
2007-04-06 1:31 ` Jeremy Fitzhardinge
2007-04-06 1:32 ` Zachary Amsden
2007-04-06 1:36 ` Jeremy Fitzhardinge
2007-04-06 1:42 ` Zachary Amsden [this message]
2007-04-06 1:19 ` Zachary Amsden
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=4615A579.10103@vmware.com \
--to=zach@vmware.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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.