mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Joerg Roedel <joro@8bytes.org>,
	iommu@lists.linux-foundation.org, vinadhy@gmail.com,
	linux-kernel@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH v2] iommu/iova: Use raw_cpu_ptr() instead of get_cpu_ptr() for ->fq
Date: Mon, 6 Nov 2017 08:43:34 -0700	[thread overview]
Message-ID: <20171106084334.639512ea@t450s.home> (raw)
In-Reply-To: <20171102173349.btd3b2xfklcfopmz@breakpoint.cc>

[cc +robin]

On Thu, 2 Nov 2017 18:33:50 +0100
Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:

> On 2017-09-21 17:21:40 [+0200], Sebastian Andrzej Siewior wrote:
> > get_cpu_ptr() disabled preemption and returns the ->fq object of the
> > current CPU. raw_cpu_ptr() does the same except that it not disable
> > preemption which means the scheduler can move it to another CPU after it
> > obtained the per-CPU object.
> > In this case this is not bad because the data structure itself is
> > protected with a spin_lock. This change shouldn't matter however on RT
> > it does because the sleeping lock can't be accessed with disabled
> > preemption.  
> 
> Did this make to your tree Jörg?

Hi Sebastian,

Joerg is out on paternity leave through the end of the year, I'm
filling in in the interim.  I hadn't looked for patches this far back,
so thanks for pointing it out.  Robin, any comments?  Thanks,

Alex

> > Cc: Joerg Roedel <joro@8bytes.org>
> > Cc: iommu@lists.linux-foundation.org
> > Reported-by: vinadhy@gmail.com
> > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> > ---
> > On 2017-09-19 11:41:19 [+0200], Joerg Roedel wrote:  
> > > Hi Sebastian,  
> > Hi Jörg,
> >   
> > > I moved the flushing to driver/iommu/iova.c to share it with the Intel
> > > IOMMU and possibly other drivers too, so this patch does no longer apply
> > > to v4.14-rc1. Can you update the patch to these changes?  
> > 
> > Sure.
> > 
> > v1…v2: move the change from amd_iommu.c to iova.c
> > 
> >  drivers/iommu/iova.c | 4 +---
> >  1 file changed, 1 insertion(+), 3 deletions(-)
> > 
> > diff --git a/drivers/iommu/iova.c b/drivers/iommu/iova.c
> > index 33edfa794ae9..b30900025c62 100644
> > --- a/drivers/iommu/iova.c
> > +++ b/drivers/iommu/iova.c
> > @@ -570,7 +570,7 @@ void queue_iova(struct iova_domain *iovad,
> >  		unsigned long pfn, unsigned long pages,
> >  		unsigned long data)
> >  {
> > -	struct iova_fq *fq = get_cpu_ptr(iovad->fq);
> > +	struct iova_fq *fq = raw_cpu_ptr(iovad->fq);
> >  	unsigned long flags;
> >  	unsigned idx;
> >  
> > @@ -600,8 +600,6 @@ void queue_iova(struct iova_domain *iovad,
> >  	if (atomic_cmpxchg(&iovad->fq_timer_on, 0, 1) == 0)
> >  		mod_timer(&iovad->fq_timer,
> >  			  jiffies + msecs_to_jiffies(IOVA_FQ_TIMEOUT));
> > -
> > -	put_cpu_ptr(iovad->fq);
> >  }
> >  EXPORT_SYMBOL_GPL(queue_iova);
> >  
> > -- 
> > 2.14.1
> >   
> 
> Sebastian
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2017-11-06 15:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-06 10:34 [PATCH] iommu/amd: Use raw_cpu_ptr() instead of get_cpu_ptr() for ->flush_queue Sebastian Andrzej Siewior
2017-09-19  9:41 ` Joerg Roedel
2017-09-21 15:21   ` [PATCH v2] iommu/iova: Use raw_cpu_ptr() instead of get_cpu_ptr() for ->fq Sebastian Andrzej Siewior
2017-11-02 17:33     ` Sebastian Andrzej Siewior
2017-11-06 15:43       ` Alex Williamson [this message]
2017-11-06 16:45         ` Robin Murphy
2017-11-06 20:07           ` Alex Williamson
     [not found] ` <CABp9dQUcXTAX9ggX+TAMHE2oH0SF8bcu47E=UYG9fgJdKBXEVg@mail.gmail.com>
2017-09-21 15:10   ` [PATCH] iommu/amd: Use raw_cpu_ptr() instead of get_cpu_ptr() for ->flush_queue Sebastian Andrzej Siewior

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=20171106084334.639512ea@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=vinadhy@gmail.com \
    /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

all inboxes | Powered by JetHome®