mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Zachary Amsden <zach@vmware.com>
Subject: [PATCH 0/3] i386 VMI fix for lazy MMU bug, take 3
Date: Fri, 6 Apr 2007 12:51:31 -0700	[thread overview]
Message-ID: <200704061951.l36JpVdT008372@zach-dev.vmware.com> (raw)

In light of objections to the original fix I proposed for lazy MMU
interactions between VMI and kmap_atomic in interrupt context, I
have an updated patch series.

The first is for 2.6.21; it is an urgent bugfix, please apply.
The second backs out the first; it is required to avoid conflicts
  with later work which has been done on the paravirt-ops code.
  It should be added to subsystem queues which are being held
  for 2.6.22.
The third illustrates the form the fix will likely take after the paravirt-ops
  queue is applied, but is for demonstration purposes only.

Zach

                 reply	other threads:[~2007-04-06 19:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200704061951.l36JpVdT008372@zach-dev.vmware.com \
    --to=zach@vmware.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome