From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
Avi Kivity <avi@redhat.com>, Huang Ying <ying.huang@intel.com>,
Jin Dongming <jin.dongming@np.css.fujitsu.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] Re: [PATCH v3 00/17] [uq/master] Patch queue, part IV (MCE edition)
Date: Thu, 3 Mar 2011 15:02:52 -0300 [thread overview]
Message-ID: <20110303180252.GA3608@amt.cnet> (raw)
In-Reply-To: <cover.1299052578.git.jan.kiszka@siemens.com>
On Wed, Mar 02, 2011 at 08:56:03AM +0100, Jan Kiszka wrote:
> This is mostly a rebase of the previous round, just including one
> additional ppc build fix (patch 2) for a regression in a previous part.
> Please merge.
>
> CC: David Gibson <david@gibson.dropbear.id.au>
> CC: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
> CC: Huang Ying <ying.huang@intel.com>
> CC: Jin Dongming <jin.dongming@np.css.fujitsu.com>
Applied, thanks.
prev parent reply other threads:[~2011-03-03 18:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 7:56 [Qemu-devel] [PATCH v3 00/17] [uq/master] Patch queue, part IV (MCE edition) Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 01/17] kvm: ppc: Fix breakage of kvm_arch_pre_run/process_irqchip_events Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 02/17] kvm: Fix build warning when KVM_CAP_SET_GUEST_DEBUG is lacking Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 03/17] x86: Account for MCE in cpu_has_work Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 04/17] x86: Perform implicit mcg_status reset Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 05/17] x86: Small cleanups of MCE helpers Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 06/17] x86: Refine error reporting of MCE injection services Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 07/17] x86: Optionally avoid injecting AO MCEs while others are pending Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 08/17] Synchronize VCPU states before reset Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 09/17] kvm: x86: Move MCE functions together Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 10/17] kvm: Rename kvm_arch_process_irqchip_events to async_events Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 11/17] kvm: x86: Inject pending MCE events on state writeback Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 12/17] x86: Run qemu_inject_x86_mce on target VCPU Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 13/17] kvm: x86: Consolidate TCG and KVM MCE injection code Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 14/17] kvm: x86: Clean up kvm_setup_mce Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 15/17] kvm: x86: Fail kvm_arch_init_vcpu if MCE initialization fails Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 16/17] Add qemu_ram_remap Jan Kiszka
2011-03-02 7:56 ` [Qemu-devel] [PATCH v3 17/17] KVM, MCE, unpoison memory address across reboot Jan Kiszka
2011-03-03 18:02 ` Marcelo Tosatti [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=20110303180252.GA3608@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jan.kiszka@siemens.com \
--cc=jin.dongming@np.css.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=ying.huang@intel.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).