All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A question about state machine function state_next()
Date: Mon, 1 Jun 2015 18:19:26 +0800	[thread overview]
Message-ID: <20150601101926.GB31271@dhcp-128-28.nay.redhat.com> (raw)
In-Reply-To: <20150601092124.GD20384@8bytes.org>

On 06/01/15 at 11:21am, Joerg Roedel wrote:
> Hi Baoquan,
> 
> On Mon, Jun 01, 2015 at 05:09:02PM +0800, Baoquan He wrote:
> > Then I am wondering  how amd_iommu_dma_ops is assigned. Maybe I need
> > check all functions more clearly.
> 
> The AMD IOMMU driver only uses per-device dma_ops. They are assigned to
> each device in device_dma_ops_init() at boot and in the
> device_change_notifier() on hotplug events.
> 
> 
> > Actually I am investigating how to port Zhenhua's kdump fix for intel
> > iommu to amd iommu since the similar bug happened on systems with amd
> > iommu. If you don't mind I can make these clean up during I understand
> > these iommu codes. And if Zhenhua plan to post patch for amd fix, I
> > can help review and test. Otherwise I can make some research and try
> > to post a draft patch.
> 
> Thanks for looking into this. Unfortunatly this somehow conflicts with
> my recent default-domain patch-set, which moves functionality into the
> IOMMU core and converts the AMD driver to make use of it. I have no real
> idea yet how to make both work, but it shouldn't be too hard. Maybe you can
> have a look into that patch-set too?

Yeah, sure. If you have got a plan I can help review when you post them. 

Thanks for the update.

Thanks
Baoquan

  reply	other threads:[~2015-06-01 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01  3:09 A question about state machine function state_next() Baoquan He
2015-06-01  6:42 ` Joerg Roedel
2015-06-01  9:09   ` Baoquan He
2015-06-01  9:21     ` Joerg Roedel
2015-06-01 10:19       ` Baoquan He [this message]
2015-06-01 10:33         ` Joerg Roedel
2015-06-01 11:11           ` Baoquan He
2015-06-01 11:18       ` Baoquan He
2015-06-01 12:01         ` Joerg Roedel
2015-06-01 14:01           ` Baoquan He

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=20150601101926.GB31271@dhcp-128-28.nay.redhat.com \
    --to=bhe@redhat.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.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.