From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Paul Durrant <Paul.Durrant@citrix.com>,
Keir Fraser <keir@xen.org>
Subject: Re: [Patch v4] x86/traps: improvements to {rd, wr}msr_hypervisor_regs()
Date: Tue, 8 Oct 2013 10:32:26 +0100 [thread overview]
Message-ID: <5253D12A.70808@citrix.com> (raw)
In-Reply-To: <5253E3E802000078000F97CC@nat28.tlf.novell.com>
On 08/10/13 09:52, Jan Beulich wrote:
>>>> On 07.10.13 at 15:46, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> --- a/xen/arch/x86/traps.c
>> +++ b/xen/arch/x86/traps.c
>> @@ -595,55 +595,50 @@ DO_ERROR_NOCODE(TRAP_copro_error, coprocessor_error)
>> DO_ERROR( TRAP_alignment_check, alignment_check)
>> DO_ERROR_NOCODE(TRAP_simd_error, simd_coprocessor_error)
>>
>> +/*
>> + * Returns 0 if not handled, and non-0 for error. (The calling semantics are
>> + * in need of some work)
>> + */
>> int rdmsr_hypervisor_regs(uint32_t idx, uint64_t *val)
>> {
> The comment here still isn't in line with the existing callers. Non-
> zero means success afaict. There simply is no path resulting in
> an error here so far.
>
>> + switch ( idx - base )
>> {
>> - case 0:
>> + case 0: /* Write hypercall page. Reads are invalid. Hand a #GP back. */
>> {
>> *val = 0;
>> - break;
>> + return 1;
> And the above means that there's no #GP being "handed back"
> here either.
>
> Jan
>
/sigh - Quite right. I misread the where the breaks were going in the
callers.
~Andrew
next prev parent reply other threads:[~2013-10-08 9:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 9:48 [Patch 0/2] Misc coverity fixes (set 2) Andrew Cooper
2013-10-07 9:48 ` [Patch 1/2] x86/vtd: Fix suspected data race condition in iommu_set_root_entry() Andrew Cooper
2013-10-07 10:03 ` Jan Beulich
2013-10-07 14:50 ` Zhang, Xiantao
2013-10-07 9:48 ` [Patch 2/2] x86/traps: improvements to {rd, wr}msr_hypervisor_regs() Andrew Cooper
2013-10-07 10:17 ` Jan Beulich
2013-10-07 10:51 ` Andrew Cooper
2013-10-07 11:59 ` [Patch v2] " Andrew Cooper
2013-10-07 12:01 ` [Patch v3] " Andrew Cooper
2013-10-07 12:26 ` Paul Durrant
2013-10-07 13:15 ` Andrew Cooper
2013-10-07 13:36 ` Jan Beulich
2013-10-07 13:46 ` [Patch v4] " Andrew Cooper
2013-10-08 8:52 ` Jan Beulich
2013-10-08 9:32 ` Andrew Cooper [this message]
2013-10-08 9:33 ` [Patch v5] " Andrew Cooper
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=5253D12A.70808@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).