From: Zhao Liu <zhao1.liu@linux.intel.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: "Zhao Liu" <zhao1.liu@intel.com>, "John Snow" <jsnow@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
qemu-devel@nongnu.org,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Zhenyu Wang" <zhenyu.z.wang@intel.com>
Subject: Re: [PATCH] scripts/cpu-x86-uarch-abi.py: Fix parameter error of cmd
Date: Wed, 18 Oct 2023 22:15:49 +0800 [thread overview]
Message-ID: <ZS/oleo+M0zSrf4z@liuzhao-OptiPlex-7080> (raw)
In-Reply-To: <c4dcc22b-da6b-44ae-9a0d-dcdb9b2e35f2@yandex-team.ru>
On Wed, Oct 18, 2023 at 01:18:51PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Date: Wed, 18 Oct 2023 13:18:51 +0300
> From: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
> Subject: Re: [PATCH] scripts/cpu-x86-uarch-abi.py: Fix parameter error of
> cmd
>
> On 18.10.23 13:00, Zhao Liu wrote:
> > From: Zhao Liu <zhao1.liu@intel.com>
> >
> > When run this script, there's the error:
> >
> > python3 scripts/cpu-x86-uarch-abi.py /tmp/qmp
> > Traceback (most recent call last):
> > File "/path-to-qemu/qemu/scripts/cpu-x86-uarch-abi.py", line 96, in <module>
> > cpu = shell.cmd("query-cpu-model-expansion",
> > TypeError: QEMUMonitorProtocol.cmd() takes 2 positional arguments but 3 were given
> >
> > Commit 7f521b023bc28 ("scripts/cpu-x86-uarch-abi.py: use .command()
> > instead of .cmd()") converts the the original .cmd() to .command()
> > (which was later renamed to "cmd" to replace the original one).
> >
> > But the new .cmd() only accepts typing.Mapping as the parameter instead
> > of typing.Dict (see _qmp.execute()).
> >
> > Change the paremeters of "query-cpu-model-expansion" to typing.Mapping
> > format to fix this error.
> >
> > Fixes: 7f521b023bc28 ("scripts/cpu-x86-uarch-abi.py: use .command() instead of .cmd()")
> > Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
> > ---
> > scripts/cpu-x86-uarch-abi.py | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/scripts/cpu-x86-uarch-abi.py b/scripts/cpu-x86-uarch-abi.py
> > index f6baeeff2400..052ddd751424 100644
> > --- a/scripts/cpu-x86-uarch-abi.py
> > +++ b/scripts/cpu-x86-uarch-abi.py
> > @@ -94,8 +94,8 @@
> > for name in sorted(names):
> > cpu = shell.cmd("query-cpu-model-expansion",
> > - { "type": "static",
> > - "model": { "name": name }})
> > + type="static",
> > + model={ "name": name })
> > got = {}
> > for (feature, present) in cpu["model"]["props"].items():
>
>
> Oh, right, thanks for fixing:
> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Thanks Vladimir!
-Zhao
next prev parent reply other threads:[~2023-10-18 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 10:00 [PATCH] scripts/cpu-x86-uarch-abi.py: Fix parameter error of cmd Zhao Liu
2023-10-18 10:18 ` Vladimir Sementsov-Ogievskiy
2023-10-18 14:15 ` Zhao Liu [this message]
2023-11-07 14:10 ` Zhao Liu
2023-11-07 14:15 ` Daniel P. Berrangé
2023-11-07 15:01 ` 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=ZS/oleo+M0zSrf4z@liuzhao-OptiPlex-7080 \
--to=zhao1.liu@linux.intel.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
--cc=zhao1.liu@intel.com \
--cc=zhenyu.z.wang@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).