All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sheng Yang <sheng@linux.intel.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org,
	Sheng Yang <sheng@linux.intel.com>
Subject: [PATCH v4 0/4] XSAVE enabling in QEmu
Date: Thu, 17 Jun 2010 15:18:12 +0800	[thread overview]
Message-ID: <1276759096-29104-1-git-send-email-sheng@linux.intel.com> (raw)

Notice the first three patches applied to uq/master branch of qemu-kvm, the last one
applied to qemu-kvm master branch. And the last one would only apply after the
first three merged in master branch.

WARNING: multiple messages have this Message-ID (diff)
From: Sheng Yang <sheng@linux.intel.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Sheng Yang <sheng@linux.intel.com>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v4 0/4] XSAVE enabling in QEmu
Date: Thu, 17 Jun 2010 15:18:12 +0800	[thread overview]
Message-ID: <1276759096-29104-1-git-send-email-sheng@linux.intel.com> (raw)

Notice the first three patches applied to uq/master branch of qemu-kvm, the last one
applied to qemu-kvm master branch. And the last one would only apply after the
first three merged in master branch.

             reply	other threads:[~2010-06-17  7:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17  7:18 Sheng Yang [this message]
2010-06-17  7:18 ` [Qemu-devel] [PATCH v4 0/4] XSAVE enabling in QEmu Sheng Yang
2010-06-17  7:18 ` [PATCH 1/4] qemu: kvm: Extend kvm_arch_get_supported_cpuid() to support index Sheng Yang
2010-06-17  7:18   ` [Qemu-devel] " Sheng Yang
2010-06-17  7:18 ` [PATCH 2/4] qemu: Enable XSAVE related CPUID Sheng Yang
2010-06-17  7:18   ` [Qemu-devel] " Sheng Yang
2010-06-17  7:18 ` [PATCH 3/4] qemu: kvm: Enable XSAVE live migration support Sheng Yang
2010-06-17  7:18   ` [Qemu-devel] " Sheng Yang
2010-06-17  7:40   ` Jan Kiszka
2010-06-17  7:40     ` [Qemu-devel] " Jan Kiszka
2010-06-17  8:26     ` Sheng Yang
2010-06-17  8:26       ` [Qemu-devel] " Sheng Yang
2010-06-17  8:57       ` Jan Kiszka
2010-06-17  8:57         ` [Qemu-devel] " Jan Kiszka
2010-06-17  9:53         ` Sheng Yang
2010-06-17  9:53           ` [Qemu-devel] " Sheng Yang
2010-06-17 13:25           ` Jan Kiszka
2010-06-17 13:25             ` [Qemu-devel] " Jan Kiszka
2010-06-17  7:18 ` [PATCH 4/4] qemu-kvm: " Sheng Yang
2010-06-17  7:18   ` [Qemu-devel] " Sheng Yang
2010-06-17  7:41   ` Jan Kiszka
2010-06-17  7:41     ` [Qemu-devel] " Jan Kiszka
2010-06-17  8:32     ` Sheng Yang
2010-06-17  8:32       ` [Qemu-devel] " Sheng Yang
2010-06-17  8:44       ` Jan Kiszka
2010-06-17  8:44         ` [Qemu-devel] " Jan Kiszka
2010-06-17 10:00         ` [PATCH] qemu-kvm: Replace kvm_set/get_fpu() with upstream version Sheng Yang
2010-06-17 10:00           ` [Qemu-devel] " Sheng Yang
2010-06-17 13:27           ` Jan Kiszka
2010-06-17 13:27             ` [Qemu-devel] " Jan Kiszka
2010-06-18 19:26 ` [PATCH v4 0/4] XSAVE enabling in QEmu Marcelo Tosatti
2010-06-18 19:26   ` [Qemu-devel] " Marcelo Tosatti

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=1276759096-29104-1-git-send-email-sheng@linux.intel.com \
    --to=sheng@linux.intel.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.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 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.