From: Stefano Brivio <sbrivio@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/5] qrap: Fix a number of issues
Date: Mon, 27 Feb 2023 11:25:27 +0100 [thread overview]
Message-ID: <20230227112527.01af34d3@elisabeth> (raw)
In-Reply-To: <CABJz62NDWdL_qK4a+x_d1sHLacZ=K9x829QEDk6NAOhjFwwaDg@mail.gmail.com>
On Fri, 24 Feb 2023 11:36:51 -0800
Andrea Bolognani <abologna@redhat.com> wrote:
> On Fri, Feb 24, 2023 at 07:49:44PM +0100, Andrea Bolognani wrote:
> > Andrea Bolognani (5):
> > qrap: Fix limits for PCI addresses
> > qrap: Fix support for pc machines
> > qrap: Drop args in JSON format
> > qrap: Introduce machine-specific PCI address base
> > qrap: Generate -netdev as JSON
> >
> > qrap.c | 47 +++++++++++++++++++++++++++++++++++------------
> > 1 file changed, 35 insertions(+), 12 deletions(-)
>
> Some information about testing.
>
> In order to convince myself that the changes I was working on were
> correct, I have created a few quick and dirty test scripts. You can
> find them here:
>
> https://gitlab.com/abologna/passt/-/commits/qrap-tests
>
> The commit contains a few YAML files:
>
> vmi-small-q35-passt.yaml # q35 VM with few devices
> vmi-small-pc-passt.yaml # pc VM with few devices
> vmi-big-q35-passt.yaml # q35 VM with many devices
> vmi-big-pc-passt.yaml # pc VM with many devices
>
> Each one of those, fed into KubeVirt, results in qrap being called
> with a bunch of command line arguments. These are normally passed to
> the actual QEMU binary, but in my case I've hacked qrap so that
> they're simply printed out.
If you think it's useful, by the way, feel free to submit those as a
patch for something on the lines of "test/kubevirt/qrap-tests", with
explicit licensing terms and something similar to your email as README.
We wouldn't run them automatically, I'm not sure I would personally try
them out, qrap should hopefully go away in a few months (even though
KubeVirt YAMLs could still be helpful), and... I know it's effort, so
I'm not really pushing for it, you know better.
Thanks!
--
Stefano
next prev parent reply other threads:[~2023-02-27 10:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 18:49 [PATCH 0/5] qrap: Fix a number of issues Andrea Bolognani
2023-02-24 18:49 ` [PATCH 1/5] qrap: Fix limits for PCI addresses Andrea Bolognani
2023-02-26 23:54 ` David Gibson
2023-02-24 18:49 ` [PATCH 2/5] qrap: Fix support for pc machines Andrea Bolognani
2023-02-26 23:55 ` David Gibson
2023-02-24 18:49 ` [PATCH 3/5] qrap: Drop args in JSON format Andrea Bolognani
2023-02-26 23:56 ` David Gibson
2023-02-24 18:49 ` [PATCH 4/5] qrap: Introduce machine-specific PCI address base Andrea Bolognani
2023-02-26 23:58 ` David Gibson
2023-02-24 18:49 ` [PATCH 5/5] qrap: Generate -netdev as JSON Andrea Bolognani
2023-02-27 0:00 ` David Gibson
2023-02-24 19:36 ` [PATCH 0/5] qrap: Fix a number of issues Andrea Bolognani
2023-02-27 10:25 ` Stefano Brivio [this message]
2023-02-27 13:59 ` Andrea Bolognani
2023-02-27 21:54 ` Stefano Brivio
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=20230227112527.01af34d3@elisabeth \
--to=sbrivio@redhat.com \
--cc=abologna@redhat.com \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).