qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org, "Daniel P.Berrangé" <berrange@redhat.com>,
	"Roman Bolshakov" <rbolshakov@ddn.com>,
	"Cameron Esfahani" <dirty@apple.com>
Subject: Re: [PATCH] hvf: remove unused but set variable
Date: Mon, 4 Nov 2024 14:12:05 -0800	[thread overview]
Message-ID: <4ad075ef-c14c-465c-99b4-de00390dabb1@linaro.org> (raw)
In-Reply-To: <0b140b1c-7174-4108-b504-98f9506f3fb8@linaro.org>

On 10/23/24 13:04, Pierrick Bouvier wrote:
> On 10/23/24 12:53, Alex Bennée wrote:
>> Pierrick Bouvier <pierrick.bouvier@linaro.org> writes:
>>
>>> fixes associated warning when building on MacOS.
>>>
>>> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
>>> ---
>>>    target/i386/hvf/x86_task.c | 10 +++++-----
>>>    1 file changed, 5 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/target/i386/hvf/x86_task.c b/target/i386/hvf/x86_task.c
>>> index f09bfbdda5b..cdea2ea69d9 100644
>>> --- a/target/i386/hvf/x86_task.c
>>> +++ b/target/i386/hvf/x86_task.c
>>> @@ -122,7 +122,6 @@ void vmx_handle_task_switch(CPUState *cpu, x68_segment_selector tss_sel, int rea
>>>        load_regs(cpu);
>>>    
>>>        struct x86_segment_descriptor curr_tss_desc, next_tss_desc;
>>> -    int ret;
>>>        x68_segment_selector old_tss_sel = vmx_read_segment_selector(cpu, R_TR);
>>>        uint64_t old_tss_base = vmx_read_segment_base(cpu, R_TR);
>>>        uint32_t desc_limit;
>>> @@ -138,7 +137,7 @@ void vmx_handle_task_switch(CPUState *cpu, x68_segment_selector tss_sel, int rea
>>>        if (reason == TSR_IDT_GATE && gate_valid) {
>>>            int dpl;
>>>    
>>> -        ret = x86_read_call_gate(cpu, &task_gate_desc, gate);
>>> +        x86_read_call_gate(cpu, &task_gate_desc, gate);
>>
>> If we don't care and this is the only caller we fix up
>> x86_read_call_gate not to return a value. It looks like it fails safe
>> with an empty entry (but also the function x86_read_call_gate needs the
>> printf removing).
>>
> Yes, or maybe we should check if the read was a success, or else call
> VM_PANIC("x86_read_call_gate").
> Any advice from hvf maintainers?
> 

We didn't have any feedback yet.

Would that be possible for a maintainer to pull the current series as it is?
It's functionnally equivalent, and remove this warning to have a clean 
9.2 release on this platform.

>>>    
>>>            dpl = task_gate_desc.dpl;
>>>            x68_segment_selector cs = vmx_read_segment_selector(cpu, R_CS);
>>> @@ -167,11 +166,12 @@ void vmx_handle_task_switch(CPUState *cpu, x68_segment_selector tss_sel, int rea
>>>            x86_write_segment_descriptor(cpu, &next_tss_desc, tss_sel);
>>>        }
>>>    
>>> -    if (next_tss_desc.type & 8)
>>> -        ret = task_switch_32(cpu, tss_sel, old_tss_sel, old_tss_base, &next_tss_desc);
>>> -    else
>>> +    if (next_tss_desc.type & 8) {
>>> +        task_switch_32(cpu, tss_sel, old_tss_sel, old_tss_base, &next_tss_desc);
>>> +    } else {
>>>            //ret = task_switch_16(cpu, tss_sel, old_tss_sel, old_tss_base, &next_tss_desc);
>>>            VM_PANIC("task_switch_16");
>>> +    }
>>>    
>>>        macvm_set_cr0(cpu->accel->fd, rvmcs(cpu->accel->fd, VMCS_GUEST_CR0) |
>>>                                    CR0_TS_MASK);
>>

  reply	other threads:[~2024-11-04 22:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 18:29 [PATCH] hvf: remove unused but set variable Pierrick Bouvier
2024-10-23 19:12 ` Richard Henderson
2024-10-23 19:53 ` Alex Bennée
2024-10-23 20:04   ` Pierrick Bouvier
2024-11-04 22:12     ` Pierrick Bouvier [this message]
2024-11-18 21:55 ` Pierrick Bouvier
2024-11-19 17:34 ` Paolo Bonzini
2024-11-20 17:38   ` Pierrick Bouvier

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=4ad075ef-c14c-465c-99b4-de00390dabb1@linaro.org \
    --to=pierrick.bouvier@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=dirty@apple.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rbolshakov@ddn.com \
    --cc=richard.henderson@linaro.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).