public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
	x86@kernel.org
Subject: Re: [PATCH v2 2/3] xen/pv: refactor msr access functions to support safe and unsafe accesses
Date: Tue, 4 Oct 2022 17:33:58 +0200	[thread overview]
Message-ID: <ee01b8d6-ee0c-b17d-1969-4aed41fa8666@suse.com> (raw)
In-Reply-To: <623a323c-943b-8c69-f877-a0669b9672dc@suse.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2045 bytes --]

On 04.10.22 13:03, Jan Beulich wrote:
> On 04.10.2022 10:43, Juergen Gross wrote:
>> Refactor and rename xen_read_msr_safe() and xen_write_msr_safe() to
>> support both cases of MSR accesses, safe ones and potentially GP-fault
>> generating ones.
>>
>> This will prepare to no longer swallow GPs silently in xen_read_msr()
>> and xen_write_msr().
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
> 
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> 
> Albeit ...
> 
>> @@ -933,23 +937,39 @@ static u64 xen_read_msr_safe(unsigned int msr, int *err)
>>   	return val;
>>   }
>>   
>> -static int xen_write_msr_safe(unsigned int msr, unsigned low, unsigned high)
>> +static void set_seg(unsigned int which, unsigned int low, unsigned int high,
>> +		    int *err)
>>   {
>> -	int ret;
>> -	unsigned int which;
>> -	u64 base;
>> +	u64 base = ((u64)high << 32) | low;
>> +
>> +	if (HYPERVISOR_set_segment_base(which, base) == 0)
>> +		return;
>>   
>> -	ret = 0;
>> +	if (err)
>> +		*err = -EIO;
> 
> ... I don't see a good reason to override the error code handed to us
> by the hypervisor here; I do realize though that this ...
> 
>> +	else
>> +		WARN(1, "Xen set_segment_base(%u, %llx) failed\n", which, base);
>> +}
>>   
>> +/*
>> + * Support write_msr_safe() and write_msr() semantics.
>> + * With err == NULL write_msr() semantics are selected.
>> + * Supplying an err pointer requires err to be pre-initialized with 0.
>> + */
>> +static void xen_do_write_msr(unsigned int msr, unsigned int low,
>> +			     unsigned int high, int *err)
>> +{
>>   	switch (msr) {
>> -	case MSR_FS_BASE:		which = SEGBASE_FS; goto set;
>> -	case MSR_KERNEL_GS_BASE:	which = SEGBASE_GS_USER; goto set;
>> -	case MSR_GS_BASE:		which = SEGBASE_GS_KERNEL; goto set;
>> -
>> -	set:
>> -		base = ((u64)high << 32) | low;
>> -		if (HYPERVISOR_set_segment_base(which, base) != 0)
>> -			ret = -EIO;
> 
> ... was this way before.

And on bare metal write_msr_safe() will return -EIO, too.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2022-10-04 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  8:43 [PATCH v2 0/3] xen/pv: sanitize xen pv guest msr accesses Juergen Gross
2022-10-04  8:43 ` [PATCH v2 1/3] xen/pv: allow pmu msr accesses to cause GP Juergen Gross
2022-10-04 10:58   ` Jan Beulich
2022-10-04 15:22     ` Juergen Gross
2022-10-04 15:50       ` Jan Beulich
2022-10-04 19:46   ` Boris Ostrovsky
2022-10-04  8:43 ` [PATCH v2 2/3] xen/pv: refactor msr access functions to support safe and unsafe accesses Juergen Gross
2022-10-04 11:03   ` Jan Beulich
2022-10-04 15:33     ` Juergen Gross [this message]
2022-10-04  8:43 ` [PATCH v2 3/3] xen/pv: support selecting safe/unsafe msr accesses Juergen Gross

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=ee01b8d6-ee0c-b17d-1969-4aed41fa8666@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jbeulich@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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