From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Eric Auger <eric.auger@redhat.com>,
eric.auger.pro@gmail.com, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, mst@redhat.com, jean-philippe@linaro.org,
imammedo@redhat.com, peter.maydell@linaro.org, clg@redhat.com,
yanghliu@redhat.com, zhenzhong.duan@intel.com
Cc: alex.williamson@redhat.com, jasowang@redhat.com,
pbonzini@redhat.com, berrange@redhat.com
Subject: Re: [PATCH v7 6/9] virtio-iommu: Add an option to define the input range width
Date: Wed, 6 Mar 2024 21:45:26 +0100 [thread overview]
Message-ID: <708f7eb4-f1fb-4f8e-8cba-7d270c84847c@linaro.org> (raw)
In-Reply-To: <20240306203348.65776-7-eric.auger@redhat.com>
On 6/3/24 21:32, Eric Auger wrote:
> aw-bits is a new option that allows to set the bit width of
> the input address range. This value will be used as a default for
> the device config input_range.end. By default it is set to 64 bits
> which is the current value.
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> Reviewed-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> Reviewed-by: Cédric Le Goater <clg@redhat.com>
>
> ---
>
> v1 -> v2:
> - Check the aw-bits value is within [32,64]
> ---
> include/hw/virtio/virtio-iommu.h | 1 +
> hw/virtio/virtio-iommu.c | 7 ++++++-
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/include/hw/virtio/virtio-iommu.h b/include/hw/virtio/virtio-iommu.h
> index 67ea5022af..83a52cc446 100644
> --- a/include/hw/virtio/virtio-iommu.h
> +++ b/include/hw/virtio/virtio-iommu.h
> @@ -68,6 +68,7 @@ struct VirtIOIOMMU {
> Notifier machine_done;
> bool granule_frozen;
> GranuleMode granule_mode;
> + uint8_t aw_bits;
> };
>
> #endif
> diff --git a/hw/virtio/virtio-iommu.c b/hw/virtio/virtio-iommu.c
> index aab97e1527..9b2813188b 100644
> --- a/hw/virtio/virtio-iommu.c
> +++ b/hw/virtio/virtio-iommu.c
> @@ -1314,7 +1314,11 @@ static void virtio_iommu_device_realize(DeviceState *dev, Error **errp)
> * in vfio realize
> */
> s->config.bypass = s->boot_bypass;
> - s->config.input_range.end = UINT64_MAX;
> + if (s->aw_bits < 32 || s->aw_bits > 64) {
> + error_setg(errp, "aw-bits must be within [32,64]");
Don't we need to return?
> + }
> + s->config.input_range.end =
> + s->aw_bits == 64 ? UINT64_MAX : BIT_ULL(s->aw_bits) - 1;
>
> switch (s->granule_mode) {
> case GRANULE_MODE_4K:
> @@ -1544,6 +1548,7 @@ static Property virtio_iommu_properties[] = {
> DEFINE_PROP_BOOL("boot-bypass", VirtIOIOMMU, boot_bypass, true),
> DEFINE_PROP_GRANULE_MODE("granule", VirtIOIOMMU, granule_mode,
> GRANULE_MODE_HOST),
> + DEFINE_PROP_UINT8("aw-bits", VirtIOIOMMU, aw_bits, 64),
> DEFINE_PROP_END_OF_LIST(),
> };
>
next prev parent reply other threads:[~2024-03-06 20:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 20:32 [PATCH v7 0/9] VIRTIO-IOMMU: Introduce aw-bits and granule options Eric Auger
2024-03-06 20:32 ` [PATCH v7 1/9] qdev: Add a granule_mode property Eric Auger
2024-03-06 20:32 ` [PATCH v7 2/9] virtio-iommu: Add a granule property Eric Auger
2024-03-06 20:32 ` [PATCH v7 3/9] virtio-iommu: Change the default granule to the host page size Eric Auger
2024-03-06 20:32 ` [PATCH v7 4/9] qemu-options.hx: Document the virtio-iommu-pci granule option Eric Auger
2024-03-06 20:44 ` Philippe Mathieu-Daudé
2024-03-07 7:32 ` Eric Auger
2024-03-07 10:21 ` Philippe Mathieu-Daudé
2024-03-07 10:41 ` Eric Auger
2024-03-06 20:32 ` [PATCH v7 5/9] virtio-iommu: Trace domain range limits as unsigned int Eric Auger
2024-03-06 20:32 ` [PATCH v7 6/9] virtio-iommu: Add an option to define the input range width Eric Auger
2024-03-06 20:45 ` Philippe Mathieu-Daudé [this message]
2024-03-07 7:35 ` Eric Auger
2024-03-06 20:32 ` [PATCH v7 7/9] hw/i386/q35: Set virtio-iommu aw-bits default value to 39 Eric Auger
2024-03-06 20:32 ` [PATCH v7 8/9] hw/arm/virt: Set virtio-iommu aw-bits default value to 48 Eric Auger
2024-03-06 20:32 ` [PATCH v7 9/9] qemu-options.hx: Document the virtio-iommu-pci aw-bits option Eric Auger
2024-03-06 20:48 ` Philippe Mathieu-Daudé
2024-03-07 7:40 ` Eric Auger
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=708f7eb4-f1fb-4f8e-8cba-7d270c84847c@linaro.org \
--to=philmd@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=imammedo@redhat.com \
--cc=jasowang@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=yanghliu@redhat.com \
--cc=zhenzhong.duan@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).