From: Bjorn Helgaas <helgaas@kernel.org>
To: Yongji Xie <xyjxie@linux.vnet.ibm.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, alex.williamson@redhat.com,
paulus@samba.org, aik@ozlabs.ru, gwshan@linux.vnet.ibm.com,
benh@kernel.crashing.org, mpe@ellerman.id.au,
zhong@linux.vnet.ibm.com
Subject: Re: [PATCH v5 4/4] PCI: Add a macro to set default alignment for all PCI devices
Date: Thu, 29 Sep 2016 09:00:14 -0500 [thread overview]
Message-ID: <20160929140014.GB31048@localhost> (raw)
In-Reply-To: <1473757234-5284-5-git-send-email-xyjxie@linux.vnet.ibm.com>
On Tue, Sep 13, 2016 at 05:00:34PM +0800, Yongji Xie wrote:
> When vfio passthroughs a PCI device of which MMIO BARs are
> smaller than PAGE_SIZE, guest will not handle the mmio
> accesses to the BARs which leads to mmio emulations in host.
>
> This is because vfio will not allow to passthrough one BAR's
> mmio page which may be shared with other BARs. Otherwise,
> there will be a backdoor that guest can use to access BARs
> of other guest.
>
> This patch adds a macro to set default alignment for all
> PCI devices. Then we could solve this issue on some platforms
> which would easily hit this issue because of their 64K page
> such as PowerNV platform by defining this macro as PAGE_SIZE.
>
> Signed-off-by: Yongji Xie <xyjxie@linux.vnet.ibm.com>
> ---
> arch/powerpc/include/asm/pci.h | 4 ++++
> drivers/pci/pci.c | 4 ++++
> 2 files changed, 8 insertions(+)
>
> diff --git a/arch/powerpc/include/asm/pci.h b/arch/powerpc/include/asm/pci.h
> index e9bd6cf..5e31bc2 100644
> --- a/arch/powerpc/include/asm/pci.h
> +++ b/arch/powerpc/include/asm/pci.h
> @@ -28,6 +28,10 @@
> #define PCIBIOS_MIN_IO 0x1000
> #define PCIBIOS_MIN_MEM 0x10000000
>
> +#ifdef CONFIG_PPC_POWERNV
> +#define PCIBIOS_DEFAULT_ALIGNMENT PAGE_SIZE
> +#endif
> +
> struct pci_dev;
>
> /* Values for the `which' argument to sys_pciconfig_iobase syscall. */
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 37f8062..9c61cbe 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -4959,6 +4959,10 @@ static resource_size_t pci_specified_resource_alignment(struct pci_dev *dev,
> resource_size_t align = 0;
> char *p;
>
> +#ifdef PCIBIOS_DEFAULT_ALIGNMENT
> + align = PCIBIOS_DEFAULT_ALIGNMENT;
> + *resize = false;
> +#endif
I'm a little confused about how this works.
I think this change only does something if the user specifies
"pci=resource_alignment=..." or writes to the /sys/.../resource_alignment
file, because those are the only ways to set resource_alignment_param.
If that's true, isn't the *default* to align to PAGE_SIZE? So I don't
understand what PCIBIOS_DEFAULT_ALIGNMENT changes.
And I'm hoping we can get rid of the resize flag based on the
discussion of the previous patch.
> spin_lock(&resource_alignment_lock);
> p = resource_alignment_param;
> if (pci_has_flag(PCI_PROBE_ONLY)) {
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-09-29 14:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 9:00 [PATCH v5 0/4] PCI: Introduce a way to enforce all MMIO BARs not to share PAGE_SIZE Yongji Xie
2016-09-13 9:00 ` [PATCH v5 1/4] PCI: Ignore enforced alignment when kernel uses existing firmware setup Yongji Xie
2016-09-13 9:00 ` [PATCH v5 2/4] PCI: Ignore enforced alignment to VF BARs Yongji Xie
2016-09-13 9:00 ` [PATCH v5 3/4] PCI: Add a new option for resource_alignment to reassign alignment Yongji Xie
2016-09-28 22:42 ` Bjorn Helgaas
2016-09-29 2:38 ` Yongji Xie
2016-09-29 11:54 ` Bjorn Helgaas
2016-09-30 3:56 ` Yongji Xie
2016-09-13 9:00 ` [PATCH v5 4/4] PCI: Add a macro to set default alignment for all PCI devices Yongji Xie
2016-09-29 14:00 ` Bjorn Helgaas [this message]
2016-09-30 4:13 ` Yongji Xie
2016-09-27 3:04 ` [PATCH v5 0/4] PCI: Introduce a way to enforce all MMIO BARs not to share PAGE_SIZE Yongji Xie
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=20160929140014.GB31048@localhost \
--to=helgaas@kernel.org \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=xyjxie@linux.vnet.ibm.com \
--cc=zhong@linux.vnet.ibm.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).