From: Jiang Liu <jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Yijing Wang <wangyijing-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Subject: Re: [PATCH] x86: irq_remapping: Fix the regression of hpet irq remapping
Date: Fri, 12 Sep 2014 17:02:20 +0800 [thread overview]
Message-ID: <5412B69C.8000202@linux.intel.com> (raw)
In-Reply-To: <1410512753-6428-1-git-send-email-wangyijing-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
On 2014/9/12 17:05, Yijing Wang wrote:
> Commit 71054d8841b4 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 alloc_irte() for hpet MSI, but
> have not composed and wrote its msg...
>
> Signed-off-by: Yijing Wang <wangyijing-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
> ---
> drivers/iommu/irq_remapping.c | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/iommu/irq_remapping.c b/drivers/iommu/irq_remapping.c
> index 85eb212..3541c71 100644
> --- a/drivers/iommu/irq_remapping.c
> +++ b/drivers/iommu/irq_remapping.c
> @@ -12,6 +12,7 @@
> #include <asm/processor.h>
> #include <asm/x86_init.h>
> #include <asm/apic.h>
> +#include <asm/hpet.h>
>
> #include "irq_remapping.h"
>
> @@ -332,10 +333,16 @@ static int msi_setup_remapped_irq(struct pci_dev *pdev, unsigned int irq,
>
> static int setup_hpet_msi_remapped(unsigned int irq, unsigned int id)
> {
> + int ret;
> +
> if (!remap_ops || !remap_ops->setup_hpet_msi)
> return -ENODEV;
>
> - return remap_ops->setup_hpet_msi(irq, id);
> + ret = remap_ops->setup_hpet_msi(irq, id);
> + if (ret)
> + return -EINVAL;
> +
> + return default_setup_hpet_msi(irq, id);
> }
Hi Yijing,
How about move default_setup_hpet_msi(irq, id) into
intel_setup_hpet_msi and amd.setup_hpet_msi?
Regards!
Gerry
>
> void panic_if_irq_remap(const char *msg)
>
next prev parent reply other threads:[~2014-09-12 9:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 9:05 [PATCH] x86: irq_remapping: Fix the regression of hpet irq remapping Yijing Wang
[not found] ` <1410512753-6428-1-git-send-email-wangyijing-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2014-09-12 9:02 ` Jiang Liu [this message]
[not found] ` <5412B69C.8000202-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2014-09-12 9:13 ` Yijing Wang
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=5412B69C.8000202@linux.intel.com \
--to=jiang.liu-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@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