All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vaishali Thakkar <vaishali.thakkar@vates.tech>
To: Jan Beulich <jbeulich@suse.com>
Cc: andrew.cooper3@citrix.com, roger.pau@citrix.com, wl@xen.org,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 2/3] x86/svm: Drop the suffix _guest from vmcb bit
Date: Mon, 18 Mar 2024 08:04:35 +0000	[thread overview]
Message-ID: <eebb0fb3-4ad2-429a-9200-81ad7b3fc0ab@vates.tech> (raw)
In-Reply-To: <3f8af14a-391b-46db-99cb-d7cafe126cfd@suse.com>

On 3/14/24 17:04, Jan Beulich wrote:
> On 13.03.2024 17:41, Vaishali Thakkar wrote:
>> The suffix _guest is redundant for asid bit. Drop it
>> to avoid adding extra code volume.
>>
>> While we're here, replace 0/1 with false/true and use
>> VMCB accessors instead of open coding.
>>
>> Suggested-by: Andrew Cooper <andrew.cooper3@citrix.com>
>> Signed-off-by: Vaishali Thakkar <vaishali.thakkar@vates.tech>
> 
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> with ...
> 
>> --- a/xen/arch/x86/hvm/svm/asid.c
>> +++ b/xen/arch/x86/hvm/svm/asid.c
>> @@ -37,14 +37,14 @@ void svm_asid_handle_vmrun(void)
>>       /* ASID 0 indicates that ASIDs are disabled. */
>>       if ( p_asid->asid == 0 )
>>       {
>> -        vmcb_set_guest_asid(vmcb, 1);
>> +        vmcb_set_asid(vmcb,true);
> 
> ... the blank put back that was lost here (can be done while committing).

Thanks

> Jan


  reply	other threads:[~2024-03-18  8:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 16:41 [PATCH v3 0/3] Misc changes for few VMCB bits Vaishali Thakkar
2024-03-13 16:41 ` [PATCH v3 1/3] x86/svm: Drop the _enabled suffix from vmcb bits Vaishali Thakkar
2024-03-13 16:41 ` [PATCH v3 2/3] x86/svm: Drop the suffix _guest from vmcb bit Vaishali Thakkar
2024-03-14 16:04   ` Jan Beulich
2024-03-18  8:04     ` Vaishali Thakkar [this message]
2024-03-13 16:41 ` [PATCH v3 3/3] x86/svmdebug: Print np, sev and sev_es vmcb bits Vaishali Thakkar
2024-03-14 16:05   ` Jan Beulich

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=eebb0fb3-4ad2-429a-9200-81ad7b3fc0ab@vates.tech \
    --to=vaishali.thakkar@vates.tech \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=wl@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 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.