From: Igor Mammedov <imammedo@redhat.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] i386/cpu: Drop the check of phys_bits in host_cpu_realizefn()
Date: Sat, 6 Jul 2024 16:58:02 +0200 [thread overview]
Message-ID: <20240706165802.49ec3fd8@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <20240704111231.2881016-1-xiaoyao.li@intel.com>
On Thu, 4 Jul 2024 07:12:31 -0400
Xiaoyao Li <xiaoyao.li@intel.com> wrote:
> The check of cpu->phys_bits to be in range between
> [32, TARGET_PHYS_ADDR_SPACE_BITS] in host_cpu_realizefn()
> is duplicated with check in x86_cpu_realizefn().
>
> Since the ckeck in x86_cpu_realizefn() is called later and can cover all
> teh x86 case. Remove the one in host_cpu_realizefn().
>
> Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
> target/i386/host-cpu.c | 12 +-----------
> 1 file changed, 1 insertion(+), 11 deletions(-)
>
> diff --git a/target/i386/host-cpu.c b/target/i386/host-cpu.c
> index 8b8bf5afeccf..b109c1a2221f 100644
> --- a/target/i386/host-cpu.c
> +++ b/target/i386/host-cpu.c
> @@ -75,17 +75,7 @@ bool host_cpu_realizefn(CPUState *cs, Error **errp)
> CPUX86State *env = &cpu->env;
>
> if (env->features[FEAT_8000_0001_EDX] & CPUID_EXT2_LM) {
> - uint32_t phys_bits = host_cpu_adjust_phys_bits(cpu);
> -
> - if (phys_bits &&
> - (phys_bits > TARGET_PHYS_ADDR_SPACE_BITS ||
> - phys_bits < 32)) {
> - error_setg(errp, "phys-bits should be between 32 and %u "
> - " (but is %u)",
> - TARGET_PHYS_ADDR_SPACE_BITS, phys_bits);
> - return false;
> - }
> - cpu->phys_bits = phys_bits;
> + cpu->phys_bits = host_cpu_adjust_phys_bits(cpu);
> }
> return true;
> }
next prev parent reply other threads:[~2024-07-06 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 11:12 [PATCH] i386/cpu: Drop the check of phys_bits in host_cpu_realizefn() Xiaoyao Li
2024-07-06 14:58 ` Igor Mammedov [this message]
2024-07-08 2:20 ` Zhao 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=20240706165802.49ec3fd8@imammedo.users.ipa.redhat.com \
--to=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiaoyao.li@intel.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).