From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: lazy mmu and interrupts
Date: Wed, 28 Mar 2007 10:28:58 -0700 [thread overview]
Message-ID: <460AA5DA.2090203@goop.org> (raw)
Do you disable interrupts when lazy_mmu is active? Otherwise, it seems
to me that drivers will have problems using kmap_atomic() within an
interrupt routine...
J
next reply other threads:[~2007-03-28 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 17:28 Jeremy Fitzhardinge [this message]
2007-03-28 23:12 ` lazy mmu and interrupts Zachary Amsden
2007-03-28 23:01 ` Jeremy Fitzhardinge
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=460AA5DA.2090203@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 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.