From: Anthony PERARD <anthony.perard@citrix.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: <qemu-devel@nongnu.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Paul Durrant <paul@xen.org>,
"open list:X86 Xen CPUs" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 1/2] hw/xen/xen_pt: Call default handler only if no custom one is set
Date: Tue, 22 Nov 2022 17:12:59 +0000 [thread overview]
Message-ID: <Y30DG96s9Ky1AUN0@perard.uk.xensource.com> (raw)
In-Reply-To: <20221114192011.1539233-1-marmarek@invisiblethingslab.com>
On Mon, Nov 14, 2022 at 08:20:10PM +0100, Marek Marczykowski-Górecki wrote:
> diff --git a/hw/xen/xen_pt.c b/hw/xen/xen_pt.c
> index 0ec7e52183..269bd26109 100644
> --- a/hw/xen/xen_pt.c
> +++ b/hw/xen/xen_pt.c
> @@ -255,6 +255,7 @@ static void xen_pt_pci_write_config(PCIDevice *d, uint32_t addr,
> uint32_t find_addr = addr;
> XenPTRegInfo *reg = NULL;
> bool wp_flag = false;
> + uint32_t emul_mask = 0, write_val;
>
> if (xen_pt_pci_config_access_check(d, addr, len)) {
> return;
> @@ -310,7 +311,6 @@ static void xen_pt_pci_write_config(PCIDevice *d, uint32_t addr,
> }
>
> memory_region_transaction_begin();
> - pci_default_write_config(d, addr, val, len);
>
> /* adjust the read and write value to appropriate CFC-CFF window */
> read_val <<= (addr & 3) << 3;
> @@ -370,6 +370,8 @@ static void xen_pt_pci_write_config(PCIDevice *d, uint32_t addr,
> return;
> }
>
> + emul_mask |= ( (1 << (reg->size * 8) ) - 1 ) << ((find_addr & 3) * 8);
> +
> /* calculate next address to find */
> emul_len -= reg->size;
> if (emul_len > 0) {
> @@ -396,6 +398,24 @@ static void xen_pt_pci_write_config(PCIDevice *d, uint32_t addr,
> /* need to shift back before passing them to xen_host_pci_set_block. */
> val >>= (addr & 3) << 3;
>
> + /* store emulated registers that didn't have specific hooks */
> + write_val = val;
> + for (index = 0; emul_mask; index += emul_len) {
`index` isn't used, was it meant to be use for something?
> + emul_len = 0;
> + while (emul_mask & 0xff) {
> + emul_len++;
This seems to count the number of byte that have a hook
(xen_pt_find_reg() found a `reg_entry`).
This loop should count instead the number of bytes for which no
`reg_entry` have been found, right? Shouldn't the loop count when a byte
in emul_mask is unset?
> + emul_mask >>= 8;
> + }
> + if (emul_len) {
> + uint32_t mask = ((1 << (emul_len * 8)) - 1);
> + pci_default_write_config(d, addr, write_val & mask, emul_len);
`addr` isn't updated in the loop, aren't we going to write bytes to the
wrong place? If for example "emul_mask == 0x00ff00ff" ?
> + write_val >>= emul_len * 8;
> + } else {
> + emul_mask >>= 8;
> + write_val >>= 8;
> + }
> + }
Thanks,
--
Anthony PERARD
WARNING: multiple messages have this Message-ID (diff)
From: Anthony PERARD via <qemu-devel@nongnu.org>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: <qemu-devel@nongnu.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Paul Durrant <paul@xen.org>,
"open list:X86 Xen CPUs" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 1/2] hw/xen/xen_pt: Call default handler only if no custom one is set
Date: Tue, 22 Nov 2022 17:12:59 +0000 [thread overview]
Message-ID: <Y30DG96s9Ky1AUN0@perard.uk.xensource.com> (raw)
In-Reply-To: <20221114192011.1539233-1-marmarek@invisiblethingslab.com>
On Mon, Nov 14, 2022 at 08:20:10PM +0100, Marek Marczykowski-Górecki wrote:
> diff --git a/hw/xen/xen_pt.c b/hw/xen/xen_pt.c
> index 0ec7e52183..269bd26109 100644
> --- a/hw/xen/xen_pt.c
> +++ b/hw/xen/xen_pt.c
> @@ -255,6 +255,7 @@ static void xen_pt_pci_write_config(PCIDevice *d, uint32_t addr,
> uint32_t find_addr = addr;
> XenPTRegInfo *reg = NULL;
> bool wp_flag = false;
> + uint32_t emul_mask = 0, write_val;
>
> if (xen_pt_pci_config_access_check(d, addr, len)) {
> return;
> @@ -310,7 +311,6 @@ static void xen_pt_pci_write_config(PCIDevice *d, uint32_t addr,
> }
>
> memory_region_transaction_begin();
> - pci_default_write_config(d, addr, val, len);
>
> /* adjust the read and write value to appropriate CFC-CFF window */
> read_val <<= (addr & 3) << 3;
> @@ -370,6 +370,8 @@ static void xen_pt_pci_write_config(PCIDevice *d, uint32_t addr,
> return;
> }
>
> + emul_mask |= ( (1 << (reg->size * 8) ) - 1 ) << ((find_addr & 3) * 8);
> +
> /* calculate next address to find */
> emul_len -= reg->size;
> if (emul_len > 0) {
> @@ -396,6 +398,24 @@ static void xen_pt_pci_write_config(PCIDevice *d, uint32_t addr,
> /* need to shift back before passing them to xen_host_pci_set_block. */
> val >>= (addr & 3) << 3;
>
> + /* store emulated registers that didn't have specific hooks */
> + write_val = val;
> + for (index = 0; emul_mask; index += emul_len) {
`index` isn't used, was it meant to be use for something?
> + emul_len = 0;
> + while (emul_mask & 0xff) {
> + emul_len++;
This seems to count the number of byte that have a hook
(xen_pt_find_reg() found a `reg_entry`).
This loop should count instead the number of bytes for which no
`reg_entry` have been found, right? Shouldn't the loop count when a byte
in emul_mask is unset?
> + emul_mask >>= 8;
> + }
> + if (emul_len) {
> + uint32_t mask = ((1 << (emul_len * 8)) - 1);
> + pci_default_write_config(d, addr, write_val & mask, emul_len);
`addr` isn't updated in the loop, aren't we going to write bytes to the
wrong place? If for example "emul_mask == 0x00ff00ff" ?
> + write_val >>= emul_len * 8;
> + } else {
> + emul_mask >>= 8;
> + write_val >>= 8;
> + }
> + }
Thanks,
--
Anthony PERARD
next prev parent reply other threads:[~2022-11-22 17:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 19:20 [PATCH 1/2] hw/xen/xen_pt: Call default handler only if no custom one is set Marek Marczykowski-Górecki
2022-11-14 19:20 ` [PATCH 2/2] Do not access /dev/mem in MSI-X PCI passthrough on Xen Marek Marczykowski-Górecki
2022-11-14 19:39 ` Andrew Cooper
2022-11-14 22:44 ` Marek Marczykowski-Górecki
2022-11-15 8:14 ` Jan Beulich
2022-11-15 11:38 ` Marek Marczykowski-Górecki
2022-11-15 14:05 ` Jan Beulich
2022-11-16 19:15 ` Jason Andryuk
2022-11-16 21:40 ` Marek Marczykowski-Górecki
2022-11-17 3:34 ` Marek Marczykowski-Górecki
2022-11-17 8:04 ` Jan Beulich
2022-11-17 11:15 ` Marek Marczykowski-Górecki
2022-11-17 17:29 ` Jason Andryuk
2022-11-22 17:12 ` Anthony PERARD [this message]
2022-11-22 17:12 ` [PATCH 1/2] hw/xen/xen_pt: Call default handler only if no custom one is set Anthony PERARD via
2023-09-26 23:25 ` Marek Marczykowski-Górecki
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=Y30DG96s9Ky1AUN0@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=marmarek@invisiblethingslab.com \
--cc=paul@xen.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.