qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ying Fang <fangying1@huawei.com>
Cc: lvivier@redhat.com, zhang.zhanghailiang@huawei.com,
	qemu-devel@nongnu.org, alex.chen@huawei.com, imammedo@redhat.com,
	philmd@redhat.com
Subject: Re: [PATCH v5 0/2] add new options to set smbios type 4 fields
Date: Thu, 6 Aug 2020 02:01:05 -0400	[thread overview]
Message-ID: <20200806020034-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200806035634.376-1-fangying1@huawei.com>

On Thu, Aug 06, 2020 at 11:56:32AM +0800, Ying Fang wrote:
> From: fangying <fangying1@huawei.com>
> 
> Hi, this patchset was previously posted by my teamate Heyi Guo several
> months ago, however we missed the merge window. It is reposted here to
> make it an end. Thanks.


Thanks, I will tag it for after the release.
Pls ping me after the release to make sure I don't drop it by mistake.

> Patch description:
>  
> Common VM users sometimes care about CPU speed, so we add two new
> options to allow VM vendors to present CPU speed to their users.
> Normally these information can be fetched from host smbios.
> 
> Strictly speaking, the "max speed" and "current speed" in type 4
> are not really for the max speed and current speed of processor, for
> "max speed" identifies a capability of the system, and "current speed"
> identifies the processor's speed at boot (see smbios spec), but some
> applications do not tell the differences.
> 
> Changelog:
> 
> v4 -> v5:
> - Rebase patch for lastest upstream
> 
> v3 -> v4:
> - Fix the default value when not specifying "-smbios type=4" option;
> it would be 0 instead of 2000 in previous versions
> - Use uint64_t type to check value overflow
> - Add test case to check smbios type 4 CPU speed
> - v4 https://patchwork.kernel.org/cover/11444635/
> 
> v2 -> v3:
> - Refine comments per Igor's suggestion.
> 
> v1 -> v2:
> - change "_" in option names to "-"
> - check if option value is too large to fit in SMBIOS type 4 speed
> fields.
> 
> Cc: "Michael S. Tsirkin" <mst@redhat.com>
> Cc: Igor Mammedov <imammedo@redhat.com>
> 
> Ying Fang (2):
>   hw/smbios: add options for type 4 max-speed and current-speed
>   tests/bios-tables-test: add smbios cpu speed test
> 
>  hw/smbios/smbios.c       | 36 ++++++++++++++++++++++++++++++----
>  qemu-options.hx          |  2 +-
>  tests/bios-tables-test.c | 42 ++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 75 insertions(+), 5 deletions(-)
> 
> -- 
> 2.23.0



  parent reply	other threads:[~2020-08-06 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06  3:56 [PATCH v5 0/2] add new options to set smbios type 4 fields Ying Fang
2020-08-06  3:56 ` [PATCH v5 1/2] hw/smbios: add options for type 4 max-speed and current-speed Ying Fang
2020-08-06  3:56 ` [PATCH v5 2/2] tests/bios-tables-test: add smbios cpu speed test Ying Fang
2020-08-06  6:01 ` Michael S. Tsirkin [this message]
2020-08-06  6:58   ` [PATCH v5 0/2] add new options to set smbios type 4 fields Ying Fang

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=20200806020034-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alex.chen@huawei.com \
    --cc=fangying1@huawei.com \
    --cc=imammedo@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhang.zhanghailiang@huawei.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).