From: "Andreas Färber" <afaerber@suse.de>
To: will.auld@intel.com
Cc: "jinsong.liu@intel.com" <jinsong.liu@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Gleb <gleb@redhat.com>,
"mtosatti@redhat.com" <mtosatti@redhat.com>,
Will Auld <will.auld.intel@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
"donald.d.dugger@intel.com" <donald.d.dugger@intel.com>,
"avi@redhat.com" <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V4] target-i386: Enabling IA32_TSC_ADJUST for Qemu KVM guest VMs
Date: Tue, 27 Nov 2012 05:05:26 +0100 [thread overview]
Message-ID: <50B43C06.3090602@suse.de> (raw)
In-Reply-To: <1353983386.12838.1.camel@WillAuldHomeLinux>
Am 27.11.2012 03:29, schrieb Will Auld:
> CPUID.7.0.EBX[1]=1 indicates IA32_TSC_ADJUST MSR 0x3b is supported
>
> Basic design is to emulate the MSR by allowing reads and writes to the
> hypervisor vcpu specific locations to store the value of the emulated MSRs.
> In this way the IA32_TSC_ADJUST value will be included in all reads to
> the TSC MSR whether through rdmsr or rdtsc.
>
> As this is a new MSR that the guest may access and modify its value needs
> to be migrated along with the other MRSs. The changes here are specifically
> for recognizing when IA32_TSC_ADJUST is enabled in CPUID and code added
> for migrating its value.
>
> Signed-off-by: Will Auld <will.auld@intel.com>
Better, but problems remain (not sure about line endings, didn't check
before). It seems the tabs got more rather than getting replaced with
four spaces. (And QEMU regressed to Qemu.)
For future patches you may find the following helpful to detect formal
errors early yourself (git commit --no-verify overrides):
http://blog.vmsplice.net/2011/03/how-to-automatically-run-checkpatchpl.html
Regards,
Andreas
$ scripts/checkpatch.pl ../wauld_tsc_adjust_v4.eml
ERROR: DOS line endings
#129: FILE: target-i386/cpu.h:287:
+#define MSR_TSC_ADJUST^I^I^I0x0000003b^M$
ERROR: code indent should never use tabs
#129: FILE: target-i386/cpu.h:287:
+#define MSR_TSC_ADJUST^I^I^I0x0000003b^M$
ERROR: DOS line endings
[...]
ERROR: code indent should never use tabs
#157: FILE: target-i386/kvm.c:645:
+^I^Iif (kvm_msr_list->indices[i] == MSR_TSC_ADJUST) {^M$
ERROR: DOS line endings
#158: FILE: target-i386/kvm.c:646:
+^I^I has_msr_tsc_adjust = true;^M$
ERROR: code indent should never use tabs
#158: FILE: target-i386/kvm.c:646:
+^I^I has_msr_tsc_adjust = true;^M$
[...]
total: 48 errors, 0 warnings, 91 lines checked
../wauld_tsc_adjust_v4.eml has style problems, please review. [...]
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2012-11-27 4:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 2:29 [Qemu-devel] [PATCH V4] target-i386: Enabling IA32_TSC_ADJUST for Qemu KVM guest VMs Will Auld
2012-11-27 4:05 ` Andreas Färber [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=50B43C06.3090602@suse.de \
--to=afaerber@suse.de \
--cc=avi@redhat.com \
--cc=donald.d.dugger@intel.com \
--cc=gleb@redhat.com \
--cc=jinsong.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=will.auld.intel@gmail.com \
--cc=will.auld@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).