linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
Cc: joro@8bytes.org, pbonzini@redhat.com, alex.williamson@redhat.com,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	sherry.hurwitz@amd.com
Subject: Re: [PART2 PATCH v6 12/12] svm: Implements update_pi_irte hook to setup posted interrupt
Date: Fri, 19 Aug 2016 17:04:06 +0200	[thread overview]
Message-ID: <20160819150405.GA5282@potion> (raw)
In-Reply-To: <20160819144907.GB1885@potion>

2016-08-19 16:49+0200, Radim Krčmář:
>   Minor design note:
>   To make the usage of "struct amd_ir_data" safer, we could pass "struct
>   list_head" into irq_set_vcpu_affinity(), instead of returning "struct
>   amd_ir_data *".
> 
>   irq_set_vcpu_affinity() would add "struct amd_ir_data" to the list only
>   if ir_data was not already in some list and report whether the list
>   was modified.

No, this would not simplify the search.  An important point of list_head
in amd_ir_data was to let us know the current list.

  reply	other threads:[~2016-08-19 15:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 19:42 [PART2 PATCH v6 00/12] iommu/AMD: Introduce IOMMU AVIC support Suravee Suthikulpanit
2016-08-18 19:42 ` [PART2 PATCH v6 01/12] iommu/amd: Detect and enable guest vAPIC support Suravee Suthikulpanit
2016-08-18 19:42 ` [PART2 PATCH v6 02/12] iommu/amd: Move and introduce new IRTE-related unions and structures Suravee Suthikulpanit
2016-08-18 19:42 ` [PART2 PATCH v6 03/12] iommu/amd: Introduce interrupt remapping ops structure Suravee Suthikulpanit
2016-08-18 19:42 ` [PART2 PATCH v6 04/12] iommu/amd: Add support for multiple IRTE formats Suravee Suthikulpanit
2016-08-18 19:42 ` [PART2 PATCH v6 05/12] iommu/amd: Detect and initialize guest vAPIC log Suravee Suthikulpanit
2016-08-18 19:42 ` [PART2 PATCH v6 06/12] iommu/amd: Adding GALOG interrupt handler Suravee Suthikulpanit
2016-08-18 19:42 ` [PART2 PATCH v6 07/12] iommu/amd: Introduce amd_iommu_update_ga() Suravee Suthikulpanit
2016-08-22  5:50   ` kbuild test robot
2016-08-18 19:42 ` [PART2 PATCH v6 08/12] iommu/amd: Implements irq_set_vcpu_affinity() hook to setup vapic mode for pass-through devices Suravee Suthikulpanit
2016-08-18 19:42 ` [PART2 PATCH v6 09/12] iommu/amd: Enable vAPIC interrupt remapping mode by default Suravee Suthikulpanit
2016-08-18 19:42 ` [PART2 PATCH v6 10/12] svm: Introduces AVIC per-VM ID Suravee Suthikulpanit
2016-08-19 13:26   ` Radim Krčmář
2016-08-18 19:42 ` [PART2 PATCH v6 11/12] svm: Introduce AMD IOMMU avic_ga_log_notifier Suravee Suthikulpanit
2016-08-18 19:42 ` [PART2 PATCH v6 12/12] svm: Implements update_pi_irte hook to setup posted interrupt Suravee Suthikulpanit
2016-08-19 14:49   ` Radim Krčmář
2016-08-19 15:04     ` Radim Krčmář [this message]
2016-08-22  9:19     ` Suravee Suthikulpanit
2016-08-22 10:09       ` Suravee Suthikulpanit
2016-08-22 15:16         ` Radim Krčmář
2016-08-23 10:51   ` kbuild 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=20160819150405.GA5282@potion \
    --to=rkrcmar@redhat.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=alex.williamson@redhat.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sherry.hurwitz@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 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).