To all X.Org Foundation Members:
The election for the X.Org Foundation Board of Directors will begin on
22 March 2021. We have 6 candidates who are running for 4 seats. They
are (in alphabetical order):
Samuel Iglesias Gonsálvez
Manasi Navare
Lyude Paul
Rodrigo Siqueira
Lu
On Mon, 2021-03-15 at 09:53 +0100, Mike Galbraith wrote:
> On Mon, 2021-03-15 at 09:05 +0100, Christian König wrote:
> > Hi Mike,
> >
> > I'm pretty sure your bisection is a bit off.
>
> (huh?) Ah crap, yup, the spew from hell you plugged obliterated the
> lockdep gripe I was grepping for as go/nog
On Sun, Mar 14, 2021 at 11:04 PM wrote:
>
> https://forum.artixlinux.org/index.php/topic,2083.msg14006.html#msg14006
> https://forum.artixlinux.org/index.php/topic,2383.new.html#new
>
> It is going to blow up many more now, the freeze bug may take days, weeks or
> months to appear, now with this
On Mon, 2021-03-15 at 09:05 +0100, Christian König wrote:
> Hi Mike,
>
> I'm pretty sure your bisection is a bit off.
(huh?) Ah crap, yup, the spew from hell you plugged obliterated the
lockdep gripe I was grepping for as go/nogo, and off into lala land we
go.. twice.. whee :) Oh well, the orderi
Hi Mike,
I'm pretty sure your bisection is a bit off.
The patch you mentioned is completely unrelated to Nouveau and I think
the code path in question is not even used by this driver.
Regards,
Christian.
Am 14.03.21 um 05:48 schrieb Mike Galbraith:
This little bugger bisected to...
> - /*XXX: atomic? */
> - return (fa->access == 0 || fa->access == 3) -
> -(fb->access == 0 || fb->access == 3);
> + /* Atomic access (2) has highest priority */
> + return (-1*(fa->access == 2) + (fa->access == 0 || fa->access == 3)) -
> +(-1*(fb->access ==
> +Not all devices support atomic access to system memory. To support atomic
> +operations to a shared virtual memory page such a device needs access to that
> +page which is exclusive of any userspace access from the CPU. The
> +``make_device_exclusive_range()`` function can be used to make a memo
On Fri, Mar 12, 2021 at 07:38:46PM +1100, Alistair Popple wrote:
> The behaviour of try_to_unmap_one() is difficult to follow because it
> performs different operations based on a fairly large set of flags used
> in different combinations.
>
> TTU_MUNLOCK is one such flag. However it is exclusivel
On Fri, Mar 12, 2021 at 07:38:44PM +1100, Alistair Popple wrote:
> Remove the migration and device private entry_to_page() and
> entry_to_pfn() inline functions and instead open code them directly.
> This results in shorter code which is easier to understand.
I think this commit log should mention
