From: Juerg Haefliger <juergh@proton.me>
To: "Petr Tesařík" <petr@tesarici.cz>
Cc: Petr Tesarik <petrtesarik@huaweicloud.com>,
Christoph Hellwig <hch@lst.de>, Jonathan Corbet <corbet@lwn.net>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>, Borislav Petkov <bp@suse.de>,
"Paul E. McKenney" <paulmck@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Kim Phillips <kim.phillips@amd.com>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:DMA MAPPING HELPERS" <iommu@lists.linux.dev>,
Roberto Sassu <roberto.sassu@huawei.com>,
Alexander Graf <graf@amazon.com>
Subject: Re: [RFC v1 3/4] swiotlb: Allow dynamic allocation of bounce buffers
Date: Thu, 06 Apr 2023 11:44:55 +0000 [thread overview]
Message-ID: <20230406134440.72959135@gollum> (raw)
In-Reply-To: <20230331110043.7b1ddfa3@meshulam.tesarici.cz>
[-- Attachment #1: Type: text/plain, Size: 5672 bytes --]
On Fri, 31 Mar 2023 11:00:43 +0200
Petr Tesařík <petr@tesarici.cz> wrote:
> Hi Juerg,
>
> On Fri, 31 Mar 2023 07:26:09 +0000
> Juerg Haefliger <juergh@proton.me> wrote:
>
> > On Tue, 28 Mar 2023 09:54:35 +0200
> > Petr Tesarik <petrtesarik@huaweicloud.com> wrote:
> >
> >[...]
> > > Anyway, I suspected that the buffers need not be imported into the vc4
> > > driver (also hinted by Eric Anholt in a 2018 blog post [1]), and it
> > > seems I was right. I encountered the issue with Ubuntu 22.10; I
> > > installed latest openSUSE Tumbleweed yesterday, and I was not able to
> > > reproduce the issue there, most likely because the Mesa drivers have
> > > been fixed meanwhile. This makes the specific case of the Raspberry Pi 4
> > > drivers moot. The issue may still affect other combinations of drivers,
> > > but I don't have any other real-world example ATM.
> >
> > I'm only seeing this problem with Wayland, no issue when switching Ubuntu to
> > X. It seems Tumbleweed is using X by default.
>
> I know; I was the team lead of SUSE low-level graphics engineers until
> end of last year... I have just double-checked, but this output of
> wayland-info in the GNOME session accessed over RDP is quite convincing:
It sure is but how did you get that?? For me it's:
$ wayland-info
failed to create display: No such file or directory
And from strace:
connect(3, {sa_family=AF_UNIX, sun_path="/run/user/1000/wayland-0"}, 27) = -1 ENOENT (No such file or directory)
Which is kind of expected when running X, no?
$ ps -ef | grep -iP 'xorg|wayland'
opensuse 1377 1375 0 09:13 tty2 00:00:16 /usr/bin/Xorg.bin vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3
What am I missing?
...Juerg
> interface: 'wl_compositor', version: 5, name: 1
> interface: 'wl_shm', version: 1, name: 2
> formats (fourcc):
> 0x48344258 = 'XB4H'
> 0x48344241 = 'AB4H'
> 0x48345258 = 'XR4H'
> 0x48345241 = 'AR4H'
> 0x30334258 = 'XB30'
> 0x30334241 = 'AB30'
> 0x30335258 = 'XR30'
> 0x30335241 = 'AR30'
> 0x36314752 = 'RG16'
> 0x34324258 = 'XB24'
> 0x34324241 = 'AB24'
> 1 = 'XR24'
> 0 = 'AR24'
> interface: 'wl_output', version: 3, name: 3
> x: 0, y: 0, scale: 1,
> physical_width: 430 mm, physical_height: 270 mm,
> make: 'FUS', model: 'P20W-5 ECO',
> subpixel_orientation: unknown, output_transform: normal,
> mode:
> width: 1680 px, height: 1050 px, refresh: 59.954 Hz,
> flags: current preferred
> interface: 'zxdg_output_manager_v1', version: 3, name: 4
> xdg_output_v1
> output: 3
> name: 'HDMI-1'
> description: 'Fujitsu Siemens Computers GmbH 20"'
> logical_x: 0, logical_y: 0
> logical_width: 1680, logical_height: 1050
> interface: 'wl_data_device_manager', version: 3, name: 5
> interface: 'zwp_primary_selection_device_manager_v1', version: 1, name: 6
> interface: 'wl_subcompositor', version: 1, name: 7
> interface: 'xdg_wm_base', version: 4, name: 8
> interface: 'gtk_shell1', version: 5, name: 9
> interface: 'wp_viewporter', version: 1, name: 10
> interface: 'zwp_pointer_gestures_v1', version: 3, name: 11
> interface: 'zwp_tablet_manager_v2', version: 1, name: 12
> interface: 'wl_seat', version: 8, name: 13
> name: seat0
> capabilities: pointer keyboard
> keyboard repeat rate: 33
> keyboard repeat delay: 500
> interface: 'zwp_relative_pointer_manager_v1', version: 1, name: 14
> interface: 'zwp_pointer_constraints_v1', version: 1, name: 15
> interface: 'zxdg_exporter_v1', version: 1, name: 16
> interface: 'zxdg_importer_v1', version: 1, name: 17
> interface: 'zwp_linux_dmabuf_v1', version: 3, name: 18
> formats (fourcc) and modifiers (names):
> 0x48344258 = 'XB4H'; 0x00ffffffffffffff = INVALID
> 0x48344241 = 'AB4H'; 0x00ffffffffffffff = INVALID
> 0x36314752 = 'RG16'; 0x00ffffffffffffff = INVALID
> 0x30334258 = 'XB30'; 0x00ffffffffffffff = INVALID
> 0x30335258 = 'XR30'; 0x00ffffffffffffff = INVALID
> 0x30334241 = 'AB30'; 0x00ffffffffffffff = INVALID
> 0x30335241 = 'AR30'; 0x00ffffffffffffff = INVALID
> 0x34324258 = 'XB24'; 0x00ffffffffffffff = INVALID
> 0x34325258 = 'XR24'; 0x00ffffffffffffff = INVALID
> 0x34324241 = 'AB24'; 0x00ffffffffffffff = INVALID
> 0x34325241 = 'AR24'; 0x00ffffffffffffff = INVALID
> interface: 'wp_single_pixel_buffer_manager_v1', version: 1, name: 19
> interface: 'zwp_keyboard_shortcuts_inhibit_manager_v1', version: 1, name: 20
> interface: 'zwp_text_input_manager_v3', version: 1, name: 21
> interface: 'wp_presentation', version: 1, name: 22
> presentation clock id: 1 (CLOCK_MONOTONIC)
> interface: 'xdg_activation_v1', version: 1, name: 23
>
> Petr T
[-- Attachment #2: attachment.sig --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2023-04-06 12:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 12:28 [RFC v1 0/4] Allow dynamic allocation of software IO TLB bounce buffers Petr Tesarik
2023-03-20 12:28 ` [RFC v1 1/4] dma-mapping: introduce the DMA_ATTR_MAY_SLEEP attribute Petr Tesarik
2023-03-28 3:57 ` Christoph Hellwig
2023-03-28 7:21 ` Petr Tesarik
2023-04-07 5:52 ` Christoph Hellwig
2023-03-31 13:06 ` Bagas Sanjaya
2023-03-20 12:28 ` [RFC v1 2/4] swiotlb: Move code around in preparation for dynamic bounce buffers Petr Tesarik
2023-03-20 12:28 ` [RFC v1 3/4] swiotlb: Allow dynamic allocation of " Petr Tesarik
2023-03-28 4:07 ` Christoph Hellwig
2023-03-28 7:54 ` Petr Tesarik
2023-03-28 12:43 ` Petr Tesarik
2023-04-07 5:57 ` Christoph Hellwig
2023-04-07 10:15 ` Petr Tesařík
2023-04-13 11:09 ` Petr Tesarik
2023-04-21 13:03 ` Petr Tesařík
2023-04-21 14:58 ` Robin Murphy
2023-04-21 15:09 ` Petr Tesařík
2023-04-24 6:03 ` Christoph Hellwig
2023-03-31 7:26 ` Juerg Haefliger
2023-03-31 9:00 ` Petr Tesařík
2023-04-06 11:44 ` Juerg Haefliger [this message]
2023-05-11 10:36 ` Petr Tesařík
2023-04-07 5:55 ` Christoph Hellwig
2023-04-07 10:46 ` Petr Tesařík
2023-04-11 3:51 ` Christoph Hellwig
2023-03-20 12:28 ` [RFC v1 4/4] swiotlb: Add an option to allow dynamic " Petr Tesarik
2023-03-27 11:06 ` [RFC v1 0/4] Allow dynamic allocation of software IO TLB " Petr Tesarik
2023-04-07 6:00 ` Christoph Hellwig
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=20230406134440.72959135@gollum \
--to=juergh@proton.me \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=damien.lemoal@opensource.wdc.com \
--cc=graf@amazon.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=kim.phillips@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=paulmck@kernel.org \
--cc=petr@tesarici.cz \
--cc=petrtesarik@huaweicloud.com \
--cc=rdunlap@infradead.org \
--cc=roberto.sassu@huawei.com \
--cc=robin.murphy@arm.com \
--cc=rostedt@goodmis.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 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).