All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yajun Deng" <yajun.deng@linux.dev>
To: "Thomas Gleixner" <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq: Keep affinity_hint unchanged if it has a value
Date: Wed, 12 Mar 2025 10:28:30 +0000	[thread overview]
Message-ID: <5f6f0c575aa00e61ec2a6a3b90df8e20a71b5900@linux.dev> (raw)
In-Reply-To: <87h63yzkb7.ffs@tglx>

March 12, 2025 at 5:10 PM, "Thomas Gleixner" <tglx@linutronix.de mailto:tglx@linutronix.de?to=%22Thomas%20Gleixner%22%20%3Ctglx%40linutronix.de%3E > wrote:


> 
> On Wed, Mar 12 2025 at 03:20, Yajun Deng wrote:
> 
> > 
> > March 11, 2025 at 10:14 PM, "Thomas Gleixner" <tglx@linutronix.de> wrote:
> > 
> > > 
> > > > For example, if affinity_hint points to smp_affinity, smp_affinity
> > >  > is changed by the user, and affinity_hint would chang. affinity_hint
> > >  > couldn't as a hint to the user, it should keep the value if it has.
> > >  
> > >  What is 'smp_affinity'?
> > > 
> >  It's 'desc->irq_common_data.affinity'.
> > 
> Which has no business to end up in the affinity hint.
>  
> 
> > 
> > > 
> > > I really fail to understand the problem you are trying to solve.
> > > 
> >  irq_update_affinity_hint(irq, desc->irq_common_data.affinity);
> > 
> >  As in this code, this means affinity_hint points to smp_affinity.
> > 
> This code does not exist and no driver should ever invoke
> irq_update_affinity_hint() that way. The hint is a cpu mask managed by
> the driver and not something the driver pulls out of a data structure
> which it has no business to fiddle with.
>

Okay, I got it. Thank you!
 
> Thanks
> 
>  tglx
>

  reply	other threads:[~2025-03-12 10:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11  1:33 [PATCH] genirq: Keep affinity_hint unchanged if it has a value Yajun Deng
2025-03-11 14:14 ` Thomas Gleixner
2025-03-12  3:20   ` Yajun Deng
2025-03-12  9:10     ` Thomas Gleixner
2025-03-12 10:28       ` Yajun Deng [this message]
2025-03-11 18:51 ` kernel test robot
2025-03-11 19:55 ` kernel test robot

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=5f6f0c575aa00e61ec2a6a3b90df8e20a71b5900@linux.dev \
    --to=yajun.deng@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.