From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Yijing Wang <wangyijing-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Jiang Liu <jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Subject: Re: [PATCH v2] x86: irq_remapping: Fix the regression of hpet irq remapping
Date: Thu, 25 Sep 2014 19:12:58 +0200 [thread overview]
Message-ID: <20140925171258.GD28786@8bytes.org> (raw)
In-Reply-To: <1410946339-27764-1-git-send-email-wangyijing-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
On Wed, Sep 17, 2014 at 05:32:19PM +0800, Yijing Wang wrote:
> Commit 71054d8841b4 ("x86, hpet: Introduce x86_msi_ops.setup_hpet_msi")
> introduced x86_msi_ops.setup_hpet_msi to setup hpet MSI irq
> when irq remapping enabled. This caused a regression of
> hpet MSI irq remapping.
>
> Original code flow before commit 71054d8841b4:
> hpet_setup_msi_irq()
> arch_setup_hpet_msi()
> setup_hpet_msi_remapped()
> remap_ops->setup_hpet_msi()
> alloc_irte()
> msi_compose_msg()
> hpet_msi_write()
> ...
>
> Current code flow after commit 71054d8841b4:
> hpet_setup_msi_irq()
> x86_msi.setup_hpet_msi()
> setup_hpet_msi_remapped()
> intel_setup_hpet_msi()
> alloc_irte()
>
> Currently, we only call alloc_irte() for hpet MSI, but
> do not composed and wrote its msg...
>
> Signed-off-by: Yijing Wang <wangyijing-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
> ---
> v1->v2: rename remap_ops->setup_hpet_msi to remap_ops->alloc_hpet_msi.
> ---
> drivers/iommu/amd_iommu.c | 4 ++--
> drivers/iommu/intel_irq_remapping.c | 4 ++--
> drivers/iommu/irq_remapping.c | 11 +++++++++--
> drivers/iommu/irq_remapping.h | 2 +-
> 4 files changed, 14 insertions(+), 7 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2014-09-25 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 9:32 [PATCH v2] x86: irq_remapping: Fix the regression of hpet irq remapping Yijing Wang
[not found] ` <1410946339-27764-1-git-send-email-wangyijing-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2014-09-25 17:12 ` Joerg Roedel [this message]
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=20140925171258.GD28786@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=wangyijing-hv44wF8Li93QT0dZR+AlfA@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).