From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 0/9] KVM: Flush out my patch queue
Date: Fri, 05 Jan 2007 09:48:55 +0200 [thread overview]
Message-ID: <459E02E7.5020407@qumranet.com> (raw)
This patchset is mostly fallout from the mmu stuff that I've neglected
to integrate with the main patchset sent yesterday. It includes a
fashionable missing dirty bit fix, and other fixes and cleanups.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2007-01-05 7:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 7:48 Avi Kivity [this message]
[not found] ` <459E02E7.5020407-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-05 7:50 ` [PATCH 1/9] KVM: Improve reporting of vmwrite errors Avi Kivity
2007-01-05 7:51 ` [PATCH 2/9] KVM: Initialize vcpu->kvm a little earlier Avi Kivity
2007-01-05 7:52 ` [PATCH 3/9] KVM: Avoid oom on cr3 switch Avi Kivity
2007-01-05 7:53 ` [PATCH 4/9] KVM: Add missing 'break' Avi Kivity
2007-01-05 7:54 ` [PATCH 5/9] KVM: Don't set guest cr3 from vmx_vcpu_setup() Avi Kivity
2007-01-05 7:55 ` [PATCH 6/9] KVM: MMU: Add missing dirty bit Avi Kivity
2007-01-05 7:56 ` [PATCH 7/9] KVM: Make loading cr3 more robust Avi Kivity
2007-01-05 7:57 ` [PATCH 8/9] KVM: Simplify mmu_alloc_roots() Avi Kivity
2007-01-05 7:58 ` [PATCH 9/9] KVM: Simplify test for interrupt window Avi Kivity
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=459E02E7.5020407@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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