Hi,
On Wednesday, 13 March 2019 14:29:28 CET Marc-André Lureau wrote:
> > On Wednesday, 13 March 2019 00:03:26 CET Marek Olšák wrote:
> > > The env var workaround is fine.
> > >
> > > Thread affinity is used for cache topology related optimizations. I think
> > > it's a mistake to treat it only
On Wed, Mar 13, 2019 at 02:29:28PM +0100, Marc-André Lureau wrote:
> Hi
>
> On Wed, Mar 13, 2019 at 8:53 AM Mathias Fröhlich
> wrote:
> >
> > Marek, Marc-Andre,
> >
> > On Wednesday, 13 March 2019 00:03:26 CET Marek Olšák wrote:
> > > The env var workaround is fine.
> > >
> > > Thread affinity
Hi
On Wed, Mar 13, 2019 at 8:53 AM Mathias Fröhlich
wrote:
>
> Marek, Marc-Andre,
>
> On Wednesday, 13 March 2019 00:03:26 CET Marek Olšák wrote:
> > The env var workaround is fine.
> >
> > Thread affinity is used for cache topology related optimizations. I think
> > it's a mistake to treat it
Hi,
On 12.3.2019 10.59, Marc-André Lureau wrote:
On Fri, Mar 1, 2019 at 12:13 PM Mathias Fröhlich
wrote:
On Friday, 1 March 2019 12:15:08 CET Eero Tamminen wrote:
On 1.3.2019 11.12, Michel Dänzer wrote:
On 2019-02-28 8:41 p.m., Marek Olšák wrote:
On Thu, Feb 28, 2019 at 1:37 PM Eero
Marek, Marc-Andre,
On Wednesday, 13 March 2019 00:03:26 CET Marek Olšák wrote:
> The env var workaround is fine.
>
> Thread affinity is used for cache topology related optimizations. I think
> it's a mistake to treat it only as a resource allocation tool.
For a shorter term solution to the
Hi,
On Tuesday, 12 March 2019 09:59:17 CET Marc-André Lureau wrote:
> Hi
>
> On Fri, Mar 1, 2019 at 12:13 PM Mathias Fröhlich
> wrote:
> >
> > On Friday, 1 March 2019 12:15:08 CET Eero Tamminen wrote:
> > > Hi,
> > >
> > > On 1.3.2019 11.12, Michel Dänzer wrote:
> > > > On 2019-02-28 8:41 p.m.,
On Tue, Mar 12, 2019 at 9:59 AM Marc-André Lureau
wrote:
>
> Hi
>
> On Fri, Mar 1, 2019 at 12:13 PM Mathias Fröhlich
> wrote:
> >
> > On Friday, 1 March 2019 12:15:08 CET Eero Tamminen wrote:
> > > Hi,
> > >
> > > On 1.3.2019 11.12, Michel Dänzer wrote:
> > > > On 2019-02-28 8:41 p.m., Marek
The env var workaround is fine.
Thread affinity is used for cache topology related optimizations. I think
it's a mistake to treat it only as a resource allocation tool.
Marek
On Tue, Mar 12, 2019, 1:59 AM Marc-André Lureau
wrote:
> Hi
>
> On Fri, Mar 1, 2019 at 12:13 PM Mathias Fröhlich
>
Hi
On Fri, Mar 1, 2019 at 12:13 PM Mathias Fröhlich
wrote:
>
> On Friday, 1 March 2019 12:15:08 CET Eero Tamminen wrote:
> > Hi,
> >
> > On 1.3.2019 11.12, Michel Dänzer wrote:
> > > On 2019-02-28 8:41 p.m., Marek Olšák wrote:
> > >>> On Thu, Feb 28, 2019 at 1:37 PM Eero Tamminen
> > >>>
> >
Hi Drew
On Mon, Mar 4, 2019 at 8:01 PM Drew Davenport wrote:
>
> We ran into a similar issue with this syscall in Chrome OS. This patch
> addressed the issue:
> https://lists.freedesktop.org/archives/mesa-dev/2019-February/215721.html
>
> Does it help in this case as well?
That doesn't work,
We ran into a similar issue with this syscall in Chrome OS. This patch
addressed the issue:
https://lists.freedesktop.org/archives/mesa-dev/2019-February/215721.html
Does it help in this case as well?
On Wed, Feb 27, 2019 at 4:13 PM wrote:
>
> From: Marc-André Lureau
>
> Since commit
FYI, starting with AMD Ryzen, multithreaded apps and libs pretty much have
to change thread affinity to get good performance out of multithreading.
Marek
On Thu, Feb 28, 2019, 11:41 AM Marek Olšák wrote:
> On Thu, Feb 28, 2019 at 11:13 AM Marc-André Lureau <
> marcandre.lur...@gmail.com>
On Friday, 1 March 2019 12:15:08 CET Eero Tamminen wrote:
> Hi,
>
> On 1.3.2019 11.12, Michel Dänzer wrote:
> > On 2019-02-28 8:41 p.m., Marek Olšák wrote:
> >>> On Thu, Feb 28, 2019 at 1:37 PM Eero Tamminen
> Why distro versions of Qemu filter sched_setaffinity() syscall?
> >>>
> >>>
Hi,
On 1.3.2019 11.12, Michel Dänzer wrote:
On 2019-02-28 8:41 p.m., Marek Olšák wrote:
On Thu, Feb 28, 2019 at 1:37 PM Eero Tamminen
Why distro versions of Qemu filter sched_setaffinity() syscall?
(https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815889)
Daniel Berrange (berrange)
On 2019-02-28 8:41 p.m., Marek Olšák wrote:
> On Thu, Feb 28, 2019 at 11:13 AM Marc-André Lureau <
> marcandre.lur...@gmail.com> wrote:
>> On Thu, Feb 28, 2019 at 1:37 PM Eero Tamminen
>> wrote:
>>>
>>> Why distro versions of Qemu filter sched_setaffinity() syscall?
>>
>>
On Thu, Feb 28, 2019 at 11:13 AM Marc-André Lureau <
marcandre.lur...@gmail.com> wrote:
> Hi Eero!
>
> (ex-colleagues, long time ago!)
>
> On Thu, Feb 28, 2019 at 1:37 PM Eero Tamminen
> wrote:
> >
> > Hi,
> >
> > On 28.2.2019 11.57, Marc-André Lureau wrote:
> > > On Thu, Feb 28, 2019 at 1:17 AM
ubject: Re: [Mesa-dev] [PATCH] RFC: Workaround for
> pthread_setaffinity_np() seccomp filtering
>
> Hi Eero!
>
> (ex-colleagues, long time ago!)
>
> On Thu, Feb 28, 2019 at 1:37 PM Eero Tamminen
> wrote:
> >
> > Hi,
> >
> > On 28.2.2019 11.57, Marc-
Hi Eero!
(ex-colleagues, long time ago!)
On Thu, Feb 28, 2019 at 1:37 PM Eero Tamminen wrote:
>
> Hi,
>
> On 28.2.2019 11.57, Marc-André Lureau wrote:
> > On Thu, Feb 28, 2019 at 1:17 AM Marek Olšák wrote:
> >> I'd rather have something more robust than an env var, like catching
> >> SIGSYS.
Hi,
On 28.2.2019 11.57, Marc-André Lureau wrote:
On Thu, Feb 28, 2019 at 1:17 AM Marek Olšák wrote:
I'd rather have something more robust than an env var, like catching SIGSYS.
SIGSYS is info for the invoking parent, not the (Mesa) process doing the
syscall.
From "man 2 seccomp":
The
Hi
On Thu, Feb 28, 2019 at 1:17 AM Marek Olšák wrote:
>
> I'd rather have something more robust than an env var, like catching SIGSYS.
With current qemu in most distros, it defaults to SIGSYS (we switched
away from SCMP_ACT_KILL, which had other problems). With more recent
qemu/libseccomp, it
I'd rather have something more robust than an env var, like catching SIGSYS.
Marek
On Wed, Feb 27, 2019 at 6:13 PM wrote:
> From: Marc-André Lureau
>
> Since commit d877451b48a59ab0f9a4210fc736f51da5851c9a ("util/u_queue:
> add UTIL_QUEUE_INIT_SET_FULL_THREAD_AFFINITY"), mesa calls
>
From: Marc-André Lureau
Since commit d877451b48a59ab0f9a4210fc736f51da5851c9a ("util/u_queue:
add UTIL_QUEUE_INIT_SET_FULL_THREAD_AFFINITY"), mesa calls
sched_setaffinity syscall. Unfortunately, qemu crashes with SIGSYS
when sandboxing is enabled (by default with libvirt), as this syscall
is
22 matches
Mail list logo