All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <jroedel@suse.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, linux-mm@kvack.org,
	David Vrabel <david.vrabel@citrix.com>,
	Pavel Machek <pavel@ucw.cz>, Dave Airlie <airlied@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Joerg Roedel <joro@8bytes.org>
Subject: Re: [Intel-gfx] [PATCH v2] mm: Track page table modifications in __apply_to_page_range()
Date: Sat, 22 Aug 2020 18:20:38 +0200	[thread overview]
Message-ID: <20200822162038.GQ3354@suse.de> (raw)
In-Reply-To: <159809591535.32652.4016790228519688343@build.alporthouse.com>

On Sat, Aug 22, 2020 at 12:31:55PM +0100, Chris Wilson wrote:
> The active ingredient was
> 
> 7f0a002b5a21 ("x86/mm: remove vmalloc faulting")

Right, that is what bisection will point to. Thanks for collecting all
the info and updating the commit message!

Regards,

	Joerg
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <jroedel@suse.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Joerg Roedel <joro@8bytes.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	intel-gfx@lists.freedesktop.org, Pavel Machek <pavel@ucw.cz>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Dave Airlie <airlied@redhat.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	David Vrabel <david.vrabel@citrix.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] mm: Track page table modifications in __apply_to_page_range()
Date: Sat, 22 Aug 2020 18:20:38 +0200	[thread overview]
Message-ID: <20200822162038.GQ3354@suse.de> (raw)
In-Reply-To: <159809591535.32652.4016790228519688343@build.alporthouse.com>

On Sat, Aug 22, 2020 at 12:31:55PM +0100, Chris Wilson wrote:
> The active ingredient was
> 
> 7f0a002b5a21 ("x86/mm: remove vmalloc faulting")

Right, that is what bisection will point to. Thanks for collecting all
the info and updating the commit message!

Regards,

	Joerg


  reply	other threads:[~2020-08-22 16:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21 12:37 [Intel-gfx] [PATCH v2] mm: Track page table modifications in __apply_to_page_range() Joerg Roedel
2020-08-21 12:37 ` Joerg Roedel
2020-08-21 13:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-08-21 16:39 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-08-21 18:51 ` [Intel-gfx] [PATCH v2] " Chris Wilson
2020-08-21 18:51   ` Chris Wilson
2020-08-21 19:18 ` [Intel-gfx] " Linus Torvalds
2020-08-21 19:18   ` Linus Torvalds
2020-08-22 16:12   ` [Intel-gfx] " Joerg Roedel
2020-08-22 16:12     ` Joerg Roedel
2020-08-21 20:35 ` [Intel-gfx] " Andrew Morton
2020-08-21 20:35   ` Andrew Morton
2020-08-21 20:50   ` [Intel-gfx] " Chris Wilson
2020-08-21 20:50     ` Chris Wilson
2020-08-21 21:29     ` [Intel-gfx] " Pavel Machek
2020-08-21 21:29       ` Pavel Machek
2020-08-22 21:25     ` [Intel-gfx] " Pavel Machek
2020-08-22 21:25       ` Pavel Machek
2020-08-21 22:34 ` [Intel-gfx] " Andrew Morton
2020-08-21 22:34   ` Andrew Morton
2020-08-21 23:39   ` [Intel-gfx] " Chris Wilson
2020-08-21 23:39     ` Chris Wilson
2020-08-22 11:31     ` [Intel-gfx] " Chris Wilson
2020-08-22 11:31       ` Chris Wilson
2020-08-22 16:20       ` Joerg Roedel [this message]
2020-08-22 16:20         ` Joerg Roedel
2020-08-23 10:44 ` [Intel-gfx] " Pavel Machek
2020-08-23 10:44   ` Pavel Machek

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=20200822162038.GQ3354@suse.de \
    --to=jroedel@suse.de \
    --cc=airlied@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=david.vrabel@citrix.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pavel@ucw.cz \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.