From: Paolo Bonzini <pbonzini@redhat.com>
To: Cameron Esfahani <dirty@apple.com>,
Roman Bolshakov <r.bolshakov@yadro.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v1 1/3] hvf: use standard CR0 and CR4 register definitions
Date: Wed, 8 Apr 2020 10:28:09 +0200 [thread overview]
Message-ID: <c8ca2869-0dbb-1be7-6d55-bf9e34afed33@redhat.com> (raw)
In-Reply-To: <47A5AD5B-50BF-4E7B-BE64-64B97E820E8A@apple.com>
On 08/04/20 08:09, Cameron Esfahani wrote:
>>>
>>> if (efer & MSR_EFER_LME) {
>>> - if (!(old_cr0 & CR0_PG) && (cr0 & CR0_PG)) {
>>> + if (!(old_cr0 & CR0_PG_MASK) && (cr0 & CR0_PG_MASK)) {
>>> enter_long_mode(vcpu, cr0, efer);
>>> }
>>> - if (/*(old_cr0 & CR0_PG) &&*/ !(cr0 & CR0_PG)) {
>>> + if (!(cr0 & CR0_PG_MASK)) {
>> IMO the patch should only change CR0_PG to CR0_PG_MASK without removal
>> of the commented condition.
>>
>> In the next patch you're improving how long mode exit is done and
>> replacement of the comment with an implementation fits better there.
>>
> The reason I removed that code was because checkpatch.pl scolded me for a patch with code commented out.
>
> I assumed that I'd get a similar warning from patchew.org about some erroneous coding styles.
>
> So I thought the easiest thing would be to remove that code as well.
>
> But I'll defer to you or Paolo: should I remove that commented code with this patch?
checkpatch errors are not absolutely a no-no, especially if the code is
pre-existing and/or it goes away later in the patch. In this case,
since you have already written the patch it's okay to keep it as is.
Paolo
next prev parent reply other threads:[~2020-04-08 8:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 0:16 [PATCH v1 0/3] hvf: Support AVX512 guests and cleanup Cameron Esfahani via
2020-03-31 0:16 ` [PATCH v1 1/3] hvf: use standard CR0 and CR4 register definitions Cameron Esfahani via
2020-04-05 17:58 ` Roman Bolshakov
2020-04-08 6:09 ` Cameron Esfahani via
2020-04-08 8:28 ` Paolo Bonzini [this message]
2020-03-31 0:16 ` [PATCH v1 2/3] hvf: Make long mode enter and exit code clearer Cameron Esfahani via
2020-04-05 18:51 ` Roman Bolshakov
2020-04-08 6:13 ` Cameron Esfahani via
2020-03-31 0:16 ` [PATCH v1 3/3] hvf: Support AVX512 guests on capable hardware Cameron Esfahani via
2020-04-06 10:00 ` Paolo Bonzini
2020-04-08 13:56 ` Roman Bolshakov
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=c8ca2869-0dbb-1be7-6d55-bf9e34afed33@redhat.com \
--to=pbonzini@redhat.com \
--cc=dirty@apple.com \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.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).