From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: lazy mmu and interrupts
Date: Wed, 28 Mar 2007 16:01:03 -0700 [thread overview]
Message-ID: <460AF3AF.9030703@goop.org> (raw)
In-Reply-To: <460AF657.6030902@vmware.com>
Zachary Amsden wrote:
> Yup, that's a pretty serious bug. Looks like the lazy mmu code needs
> to save and restore interrupts, or alternatively, have kmap_atomic
> turn off lazy_mmu if it is enabled.
Have you seen it? I did a little lazy_mmu prototype last night and it
popped up pretty quickly.
J
prev parent reply other threads:[~2007-03-28 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 17:28 lazy mmu and interrupts Jeremy Fitzhardinge
2007-03-28 23:12 ` Zachary Amsden
2007-03-28 23:01 ` Jeremy Fitzhardinge [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=460AF3AF.9030703@goop.org \
--to=jeremy@goop.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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).