From: Avi Kivity <avi@redhat.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] Some KVM fixes
Date: Wed, 20 Apr 2011 11:28:26 +0300 [thread overview]
Message-ID: <4DAE992A.7030501@redhat.com> (raw)
In-Reply-To: <1303119773-3436-1-git-send-email-joerg.roedel@amd.com>
On 04/18/2011 12:42 PM, Joerg Roedel wrote:
> Hi,
>
> these two patches fix one issue introduced with the recent
> emulator-intercept code (the issue was there before too, but
> hidden by other workaround code which was removed in the
> mentioned patch-set).
> The second patch fixes a problem introduced with the tsc-scaling
> patch-set where the TSC was not usable anymore after a
> guest-reboot.
> All-in-all, these fixes are no -stable material.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-04-20 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 9:42 [PATCH 0/2] Some KVM fixes Joerg Roedel
2011-04-18 9:42 ` [PATCH 1/2] KVM: SVM: Fix nested sel_cr0 intercept path with decode-assists Joerg Roedel
2011-04-18 9:42 ` [PATCH 2/2] KVM: X86: Update last_guest_tsc in vcpu_put Joerg Roedel
2011-04-20 8:28 ` Avi Kivity [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=4DAE992A.7030501@redhat.com \
--to=avi@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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 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.