iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] iommu/amd: Suppress IO_PAGE_FAULTs in kdump kernel
Date: Thu, 20 Jul 2017 21:17:43 +0800	[thread overview]
Message-ID: <20170720131743.GH2344@x1> (raw)
In-Reply-To: <20170626100742.GC3737-l3A5Bk7waGM@public.gmane.org>

Hi Joerg,

On 06/26/17 at 12:07pm, Joerg Roedel wrote:
> Hi Baoquan,
> 
> On Fri, Jun 23, 2017 at 07:43:10PM +0800, Baoquan He wrote:
> > Do you think whether it's necessary to continue my kdump fix of amd iommu
> > patchset? Seems my last post was in Jan this year. I know you are very
> > busy on fixing bugs and reviewing tons of patches. Without your
> > guidance and reviewing, I absolutely can't make it. So I would like to
> > hear your suggestions and idea.
> > 
> > I focused on kaslr issues recently, now most of them have been
> > fixed. My boss discussed with me about the next plan. If you have other
> > plan, I can sync it to our team about the status of upstream.
> 
> Sorry for my silence on the patches, I have not yet found the time to
> look deeply into them. I am still interested in them, so how about you
> do a rebase/repost after the next merge window and then I will take the
> time for a more in depth review and discussion?

I have rebased the amd iommu fix patches of kdump kernel on the latest
upstream kernel, can I send them to you to have a look? Or just send to
iommu and lkml mailing list?

Thanks
Baoquan

  parent reply	other threads:[~2017-07-20 13:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16  8:15 [PATCH] iommu/amd: Suppress IO_PAGE_FAULTs in kdump kernel Joerg Roedel
     [not found] ` <1497600901-8993-1-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-06-23  8:57   ` Baoquan He
2017-06-23 11:43     ` Baoquan He
2017-06-26 10:07       ` Joerg Roedel
     [not found]         ` <20170626100742.GC3737-l3A5Bk7waGM@public.gmane.org>
2017-06-26 10:25           ` Baoquan He
2017-07-20 13:17           ` Baoquan He [this message]
2017-07-20 13:27             ` Joerg Roedel

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=20170720131743.GH2344@x1 \
    --to=bhe-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=jroedel-l3A5Bk7waGM@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).