From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org,
Alexander Duyck <alexander.duyck@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v21 QEMU 4/5] virtio-balloon: Implement support for page poison tracking feature
Date: Fri, 24 Apr 2020 09:53:54 +0200 [thread overview]
Message-ID: <20200424095354.03008d1e.cohuck@redhat.com> (raw)
In-Reply-To: <69ff8fd6-8f34-bf8a-2a8c-a1c4947383a6@redhat.com>
On Fri, 24 Apr 2020 09:07:25 +0200
David Hildenbrand <david@redhat.com> wrote:
> >> GlobalProperty hw_compat_4_2[] = {
> >> { "virtio-blk-device", "queue-size", "128"},
> >> { "virtio-scsi-device", "virtqueue_size", "128"},
> >
> > Okay, so the bit above is for after 5_0 is released then? Is there a
>
> Yes.
>
> > way to queue up a reminder or something so we get to it when the time
> > comes, or I just need to watch for 5.0 to come out and submit a patch
> > then?
>
> I think what happened usually happens is that someone introduces all the
> compat machines, sometimes directly with empty hw_compat.
>
> E.g., see
>
> commit 3eb74d2087d3bd6cb51c06a49ba94222248d2de4
> Author: Cornelia Huck <cohuck@redhat.com>
> Date: Tue Nov 12 11:48:11 2019 +0100
>
> hw: add compat machines for 5.0
>
> Add 5.0 machine types for arm/i440fx/q35/s390x/spapr.
>
> and
>
> commit 9aec2e52ce9d9632a86be2d1d0dd493722d2e7be
> Author: Cornelia Huck <cohuck@redhat.com>
> Date: Wed Jul 24 12:35:24 2019 +0200
>
> hw: add compat machines for 4.2
>
> Add 4.2 machine types for arm/i440fx/q35/s390x/spapr.
>
>
> The latter already introduced hw_compat_4_1, for examnple.
>
> @Conny, do you already have a patch for 5.1 compat patch lying around
> somewhere?
Not yet, will do so now. Thanks for the reminder, nearly forgot about
that :)
next prev parent reply other threads:[~2020-04-24 7:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 18:20 [PATCH v21 QEMU 0/5] virtio-balloon: add support for free page reporting Alexander Duyck
2020-04-22 18:20 ` [PATCH v21 QEMU 1/5] linux-headers: Update to allow renaming of free_page_report_cmd_id Alexander Duyck
2020-04-22 18:21 ` [PATCH v21 QEMU 2/5] linux-headers: update to contain virito-balloon free page reporting Alexander Duyck
2020-04-22 18:21 ` [PATCH v21 QEMU 3/5] virtio-balloon: Replace free page hinting references to 'report' with 'hint' Alexander Duyck
2020-04-24 11:23 ` David Hildenbrand
2020-04-24 14:56 ` Alexander Duyck
2020-04-24 15:11 ` David Hildenbrand
2020-04-22 18:21 ` [PATCH v21 QEMU 4/5] virtio-balloon: Implement support for page poison tracking feature Alexander Duyck
2020-04-23 8:11 ` David Hildenbrand
2020-04-23 14:46 ` Alexander Duyck
2020-04-23 16:02 ` David Hildenbrand
2020-04-23 17:49 ` Alexander Duyck
2020-04-24 7:07 ` David Hildenbrand
2020-04-24 7:53 ` Cornelia Huck [this message]
2020-04-24 7:56 ` David Hildenbrand
2020-04-22 18:21 ` [PATCH v21 QEMU 5/5] virtio-balloon: Provide an interface for free page reporting Alexander Duyck
2020-04-24 11:20 ` David Hildenbrand
2020-04-24 15:18 ` Alexander Duyck
2020-04-24 15:34 ` David Hildenbrand
2020-04-24 16:09 ` Alexander Duyck
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=20200424095354.03008d1e.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-dev@lists.oasis-open.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).