From: Javier Martinez Canillas <javierm@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>,
corbet@lwn.net, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@linux.ie,
daniel@ffwll.ch, deller@gmx.de, gregkh@linuxfoundation.org
Cc: linux-fbdev@vger.kernel.org, kvm@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Gerd Hoffmann <kraxel@redhat.com>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH v2 2/2] vfio/pci: Remove console drivers
Date: Tue, 21 Jun 2022 02:15:54 +0200 [thread overview]
Message-ID: <e6306933-45c4-f38a-bae1-3ad149d67e1b@redhat.com> (raw)
In-Reply-To: <165541193265.1955826.8778757616438743090.stgit@omen>
Hello Alex,
On 6/16/22 22:38, Alex Williamson wrote:
> Console drivers can create conflicts with PCI resources resulting in
> userspace getting mmap failures to memory BARs. This is especially
> evident when trying to re-use the system primary console for userspace
> drivers. Use the aperture helpers to remove these conflicts.
>
> Reported-by: Laszlo Ersek <lersek@redhat.com>
> Suggested-by: Gerd Hoffmann <kraxel@redhat.com>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
Patch looks good to me.
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
--
Best regards,
Javier Martinez Canillas
Linux Engineering
Red Hat
next prev parent reply other threads:[~2022-06-21 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 20:38 [PATCH v2 0/2] Improve vfio-pci primary GPU assignment behavior Alex Williamson
2022-06-16 20:38 ` [PATCH v2 1/2] drm: Implement DRM aperture helpers under video/ Alex Williamson
2022-06-21 0:14 ` Javier Martinez Canillas
2022-06-21 11:29 ` Thomas Zimmermann
2022-06-21 12:25 ` Javier Martinez Canillas
2022-06-16 20:38 ` [PATCH v2 2/2] vfio/pci: Remove console drivers Alex Williamson
2022-06-21 0:15 ` Javier Martinez Canillas [this message]
2022-06-20 11:43 ` [PATCH v2 0/2] Improve vfio-pci primary GPU assignment behavior Laszlo Ersek
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=e6306933-45c4-f38a-bae1-3ad149d67e1b@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=alex.williamson@redhat.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lersek@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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).