From: Wei Liu <wei.liu@kernel.org>
To: Nuno Das Neves <nunodasneves@linux.microsoft.com>
Cc: Wei Liu <wei.liu@kernel.org>,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, jinankjain@linux.microsoft.com,
mikelley@microsoft.com, kys@microsoft.com,
Tianyu.Lan@microsoft.com, haiyangz@microsoft.com,
decui@microsoft.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com
Subject: Re: [PATCH] x86/hyperv: Fix hv_get/set_register for nested bringup
Date: Tue, 14 Feb 2023 23:05:18 +0000 [thread overview]
Message-ID: <Y+wTrlz8nlk4h11/@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <8d0b36c0-dfca-6d4b-076d-033f9ccda4c7@linux.microsoft.com>
On Tue, Feb 14, 2023 at 02:17:52PM -0800, Nuno Das Neves wrote:
> On 2/13/2023 6:28 AM, Wei Liu wrote:
> > A few comments on style.
> >
> > On Thu, Feb 09, 2023 at 02:02:52PM -0800, Nuno Das Neves wrote:
> >> hv_get_nested_reg only translates SINT0, resulting in the wrong sint
> >> being registered by nested vmbus.
> >
> > Please put a blank line between paragraphs.
> >
>
> Ok
>
> >> Fix the issue with new utility function hv_is_sint_reg.
> >> While at it, improve clarity of hv_set_non_nested_register and hv_is_synic_reg.
> >>
> >> Signed-off-by: Nuno Das Neves <nunodasneves@linux.microsoft.com>
> >> ---
> >> arch/x86/include/asm/mshyperv.h | 11 +++++++----
> >> arch/x86/kernel/cpu/mshyperv.c | 8 ++++----
> >> 2 files changed, 11 insertions(+), 8 deletions(-)
> >>
> >> diff --git a/arch/x86/include/asm/mshyperv.h b/arch/x86/include/asm/mshyperv.h
> >> index 9ae1a344536b..684c547c1cca 100644
> >> --- a/arch/x86/include/asm/mshyperv.h
> >> +++ b/arch/x86/include/asm/mshyperv.h
> >> @@ -225,10 +225,13 @@ extern bool hv_isolation_type_snp(void);
> >>
> >> static inline bool hv_is_synic_reg(unsigned int reg)
> >> {
> >> - if ((reg >= HV_REGISTER_SCONTROL) &&
> >> - (reg <= HV_REGISTER_SINT15))
> >> - return true;
> >> - return false;
> >> + return (reg >= HV_REGISTER_SCONTROL) &&
> >> + (reg <= HV_REGISTER_SINT15);
> >> +}
> >
> > Please put a new line here.
> >
>
> Ok
>
> > I can fix these issues too if you don't end up sending a new version due
> > to other issues.
> >
> > Jinank, please take a look. The code looks sensible to me, but I would
> > like you to have a look too.
> >
>
> I'll wait for Jinank to take a look before posting another version...
>
If Jinank is happy with the change, I can just fix things up for you
before I commit this patch.
Wei.
next prev parent reply other threads:[~2023-02-14 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 22:02 [PATCH] x86/hyperv: Fix hv_get/set_register for nested bringup Nuno Das Neves
2023-02-13 14:28 ` Wei Liu
2023-02-14 22:17 ` Nuno Das Neves
2023-02-14 23:05 ` Wei Liu [this message]
2023-02-15 16:35 ` Jinank Jain
2023-02-15 22:07 ` Nuno Das Neves
2023-02-16 14:33 ` Wei Liu
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=Y+wTrlz8nlk4h11/@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=Tianyu.Lan@microsoft.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=jinankjain@linux.microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=nunodasneves@linux.microsoft.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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