From: Wei Liu <wei.liu@kernel.org>
To: Saurabh Sengar <ssengar@linux.microsoft.com>
Cc: ssengar@microsoft.com, kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
deller@gmx.de, linux-hyperv@vger.kernel.org,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] video: hyperv_fb: Allow resolutions with size > 64 MB for Gen1
Date: Thu, 28 Apr 2022 14:37:46 +0000 [thread overview]
Message-ID: <20220428143746.sya775ro5zi3kgm3@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <1651067273-6635-1-git-send-email-ssengar@linux.microsoft.com>
On Wed, Apr 27, 2022 at 06:47:53AM -0700, Saurabh Sengar wrote:
> This patch fixes a bug where GEN1 VMs doesn't allow resolutions greater
> than 64 MB size (eg 7680x4320). Unnecessary PCI check limits Gen1 VRAM
> to legacy PCI BAR size only (ie 64MB). Thus any, resolution requesting
> greater then 64MB (eg 7680x4320) would fail. MMIO region assigning this
> memory shouldn't be limited by PCI bar size.
>
> Signed-off-by: Saurabh Sengar <ssengar@linux.microsoft.com>
> ---
> drivers/video/fbdev/hyperv_fb.c | 19 +------------------
> 1 file changed, 1 insertion(+), 18 deletions(-)
>
> diff --git a/drivers/video/fbdev/hyperv_fb.c b/drivers/video/fbdev/hyperv_fb.c
> index c8e0ea2..58c304a 100644
> --- a/drivers/video/fbdev/hyperv_fb.c
> +++ b/drivers/video/fbdev/hyperv_fb.c
> @@ -1009,7 +1009,6 @@ static int hvfb_getmem(struct hv_device *hdev, struct fb_info *info)
> struct pci_dev *pdev = NULL;
> void __iomem *fb_virt;
> int gen2vm = efi_enabled(EFI_BOOT);
> - resource_size_t pot_start, pot_end;
> phys_addr_t paddr;
> int ret;
>
> @@ -1060,23 +1059,7 @@ static int hvfb_getmem(struct hv_device *hdev, struct fb_info *info)
> dio_fb_size =
> screen_width * screen_height * screen_depth / 8;
>
> - if (gen2vm) {
> - pot_start = 0;
> - pot_end = -1;
> - } else {
> - if (!(pci_resource_flags(pdev, 0) & IORESOURCE_MEM) ||
> - pci_resource_len(pdev, 0) < screen_fb_size) {
> - pr_err("Resource not available or (0x%lx < 0x%lx)\n",
> - (unsigned long) pci_resource_len(pdev, 0),
> - (unsigned long) screen_fb_size);
> - goto err1;
This restriction has been in place since day 1. Haiyang, you wrote this
driver. Can you comment on whether this change here is sensible?
Thanks,
Wei.
> - }
> -
> - pot_end = pci_resource_end(pdev, 0);
> - pot_start = pot_end - screen_fb_size + 1;
> - }
> -
> - ret = vmbus_allocate_mmio(&par->mem, hdev, pot_start, pot_end,
> + ret = vmbus_allocate_mmio(&par->mem, hdev, 0, -1,
> screen_fb_size, 0x100000, true);
> if (ret != 0) {
> pr_err("Unable to allocate framebuffer memory\n");
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2022-04-28 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 13:47 [PATCH] video: hyperv_fb: Allow resolutions with size > 64 MB for Gen1 Saurabh Sengar
2022-04-27 19:24 ` Helge Deller
2022-04-28 14:37 ` Wei Liu [this message]
2022-05-04 16:43 ` Haiyang Zhang
2022-05-04 17:05 ` Dexuan Cui
2022-05-18 18:48 ` Dexuan Cui
2022-05-19 9:08 ` Helge Deller
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=20220428143746.sya775ro5zi3kgm3@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=decui@microsoft.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ssengar@linux.microsoft.com \
--cc=ssengar@microsoft.com \
--cc=sthemmin@microsoft.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).