From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Cc: dkiper@net-space.pl, kevin.tian@intel.com,
tinnycloud@hotmail.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [GIT PULL] (xen) stable/irq stable/p2m.bugfixes stable/e820.bugfixes stable/mmu.bugfixes
Date: Thu, 19 May 2011 12:33:21 -0400 [thread overview]
Message-ID: <20110519163321.GC13186@dumpdata.com> (raw)
Hey Linus,
Please pull these four branches:
git pull git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/irq stable/p2m.bugfixes stable/e820.bugfixes stable/mmu.bugfixes
Which has ..um.. bug-fixes.
#stable/irq is based of v2.6.39-rc7 (693d92a1bbc9e42681c42ed190bd42b636ca876f)
which has one patch that cleans up the way event channels are funneled into the
right IRQ handler in Linux. The way we do the things right is pretty horrid.
In the Xen hypervisor, GSI, vectors, or virtual vectors are all funneled in their
respective event channels. On the Linux side we have to de-multiplex this
and let the right IRQ handler handle it. Except that we were overloading the
chip functions that dealt with GSI and vectors (MSI/MSI-X) causing us to have to
do some extra hack^H^H^H fancy unmasking/masking. All this is now going away.
The IRQ ACKing might be slower now, but it is much easier to understand.
#stable/p2m.bugfixes is based off v2.6.39-rc1 (0ce790e7d736cedc563e1fb4e998babf5a4dbc3d)
During save and restore we did not remember the PFN to MFN entries that were
created for the E820 PCI holes. Hence during restore we would forget them
and crash.
#stable/e820.bugfixes is based off v2.6.39-rc7 (693d92a1bbc9e42681c42ed190bd42b636ca876f)
.. has two fixes for the patches that went in 2.6.39. We were mishandling
the E820 parsing under certain conditions - workaround existed so they weren't
being pushed for 2.6.39.
#stable/mmu.bugfixes is based off v2.6.39-rc7 (693d92a1bbc9e42681c42ed190bd42b636ca876f)
.. fixes a nasty race condition. This particular bug started manifesting
itself when git commit 831d52bc153971b70e64eccfbed2b232394f22f8
("x86, mm: avoid possible bogus tlb entries by clearing prev mm_cpumask after") was
introduced.
The diff stat:
arch/x86/xen/mmu.c | 2 +-
arch/x86/xen/p2m.c | 30 ++++++++++++-
arch/x86/xen/setup.c | 6 ++-
drivers/xen/events.c | 113 ++++++++++++++++++++++++++++++++------------------
4 files changed, 107 insertions(+), 44 deletions(-)
and the full log:
Daniel Kiper (1):
xen/setup: Fix for incorrect xen_extra_mem_start initialization under 32-bit
Konrad Rzeszutek Wilk (2):
xen/setup: Ignore E820_UNUSABLE when setting 1-1 mappings.
xen/p2m: Create entries in the P2M_MFN trees's to track 1-1 mappings
Stefano Stabellini (1):
xen: do not clear and mask evtchns in __xen_evtchn_do_upcall
Tian, Kevin (1):
xen mmu: fix a race window causing leave_mm BUG()
reply other threads:[~2011-05-19 16:33 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=20110519163321.GC13186@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dkiper@net-space.pl \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tinnycloud@hotmail.com \
--cc=torvalds@linux-foundation.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