From: Thomas Gleixner <tglx@linutronix.de>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Shannon Nelson <shannon.nelson@amd.com>,
alex.williamson@redhat.com, kevin.tian@intel.com,
reinette.chatre@intel.com, kvm@vger.kernel.org,
brett.creeley@amd.com, linux-kernel@vger.kernel.org,
Leon Romanovsky <leonro@nvidia.com>
Subject: Re: [PATCH vfio] vfio/pci: remove msi domain on msi disable
Date: Tue, 19 Sep 2023 02:57:35 +0200 [thread overview]
Message-ID: <871qevx9mo.ffs@tglx> (raw)
In-Reply-To: <20230919003251.GR13795@ziepe.ca>
On Mon, Sep 18 2023 at 21:32, Jason Gunthorpe wrote:
> On Tue, Sep 19, 2023 at 02:25:32AM +0200, Thomas Gleixner wrote:
>
>> > I don't think we need to try and fix that..
>>
>> We might want to detect it and yell about it, right?
>
> It strikes me as a good idea, yes. If it doesn't cost anything.
It should not be expensive in the interrupt allocation/deallocation
path, where hardware needs to be accessed anyway. So one extra read is
not the end of the world.
Thanks,
tglx
next prev parent reply other threads:[~2023-09-19 0:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 19:14 [PATCH vfio] vfio/pci: remove msi domain on msi disable Shannon Nelson
2023-09-18 14:17 ` Jason Gunthorpe
2023-09-18 17:48 ` Nelson, Shannon
2023-09-18 23:32 ` Jason Gunthorpe
2023-09-19 0:13 ` Nelson, Shannon
2023-09-18 18:43 ` Thomas Gleixner
2023-09-18 23:37 ` Jason Gunthorpe
2023-09-18 23:47 ` Thomas Gleixner
2023-09-19 0:02 ` Jason Gunthorpe
2023-09-19 0:25 ` Thomas Gleixner
2023-09-19 0:32 ` Jason Gunthorpe
2023-09-19 0:57 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-15 7:38 kernel test robot
2023-09-15 14:22 kernel test robot
2023-09-28 1:52 ` Liu, Yujie
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=871qevx9mo.ffs@tglx \
--to=tglx@linutronix.de \
--cc=alex.williamson@redhat.com \
--cc=brett.creeley@amd.com \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=shannon.nelson@amd.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 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.