public inbox for linux-kernel@vger.kernel.org
 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 v3 07/11] iommu/amd: Introduce amd_iommu_update_ga()
Date: Mon, 11 Jul 2016 20:59:43 +0200	[thread overview]
Message-ID: <20160711185943.GA1375@potion> (raw)
In-Reply-To: <1468231899-6987-8-git-send-email-suravee.suthikulpanit@amd.com>

2016-07-11 05:11-0500, Suravee Suthikulpanit:
> From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
> 
> Introduces a new IOMMU API, amd_iommu_update_ga(), which allows
> KVM (SVM) to update existing posted interrupt IOMMU IRTE when
> load/unload vcpu.
> 
> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
> ---
> diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
> @@ -4481,4 +4481,67 @@ int amd_iommu_create_irq_domain(struct amd_iommu *iommu)
> +int amd_iommu_update_ga(u32 vcpu_id, u32 cpu, u32 ga_tag,
> +			u64 base, bool is_run)

Not just in this function does the interface between svm and iommu split
ga_tag into its two components (vcpu_id and ga_tag), but it seems that
the combined value could always be used instead ...
Is there an advantage to passing two values?

> +{
> +	unsigned long flags;
> +	struct amd_iommu *iommu;
> +
> +	if (!AMD_IOMMU_GUEST_IR_VAPIC(amd_iommu_guest_ir))
> +		return 0;
> +
> +	for_each_iommu(iommu) {
> +		struct amd_ir_data *ir_data;
> +
> +		spin_lock_irqsave(&iommu->ga_hash_lock, flags);
> +
> +		/* Note: Update all possible ir_data for a particular
> +		 * vcpu in a particular vm.
> +		 */
> +		hash_for_each_possible(iommu->ga_hash, ir_data, hnode,
> +				       AMD_IOMMU_GATAG(ga_tag, vcpu_id)) {
> +			struct irte_ga *irte = (struct irte_ga *) ir_data->entry;

(The ga_tag check is missing here too.)

> +			if (!irte->lo.fields_vapic.guest_mode)
> +				continue;
> +
> +			update_irte_ga((struct irte_ga *)ir_data->ref,
> +					ir_data->irq_2_irte.devid,
> +					base, cpu, is_run);

(The lookup leading up to here is avoidable -- svm, the caller, has the
 ability to map ga_tag into irte/ir_data directly with a pointer.
 I'm not sure if the lookup is slow enough to pardon optimization, but
 it might make the code simpler as well.)

> +			iommu_flush_irt(iommu, ir_data->irq_2_irte.devid);
> +			iommu_completion_wait(iommu);
> +		}
> +
> +		spin_unlock_irqrestore(&iommu->ga_hash_lock, flags);

  reply	other threads:[~2016-07-11 18:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 10:11 [PART2 PATCH v3 00/11] iommu/AMD: Introduce IOMMU AVIC support Suravee Suthikulpanit
2016-07-11 10:11 ` [PART2 PATCH v3 01/11] iommu/amd: Detect and enable guest vAPIC support Suravee Suthikulpanit
2016-07-11 10:11 ` [PART2 PATCH v3 02/11] iommu/amd: Move and introduce new IRTE-related unions and structures Suravee Suthikulpanit
2016-07-11 10:11 ` [PART2 PATCH v3 03/11] iommu/amd: Introduce interrupt remapping ops structure Suravee Suthikulpanit
2016-07-11 10:11 ` [PART2 PATCH v3 04/11] iommu/amd: Add support for multiple IRTE formats Suravee Suthikulpanit
2016-07-11 10:11 ` [PART2 PATCH v3 05/11] iommu/amd: Detect and initialize guest vAPIC log Suravee Suthikulpanit
2016-07-11 10:11 ` [PART2 PATCH v3 06/11] iommu/amd: Adding GALOG interrupt handler Suravee Suthikulpanit
2016-07-11 18:47   ` Radim Krčmář
2016-07-13 12:49     ` Suravee Suthikulpanit
2016-07-11 10:11 ` [PART2 PATCH v3 07/11] iommu/amd: Introduce amd_iommu_update_ga() Suravee Suthikulpanit
2016-07-11 18:59   ` Radim Krčmář [this message]
2016-07-13  8:49     ` Suravee Suthikulpanit
2016-07-11 10:11 ` [PART2 PATCH v3 08/11] iommu/amd: Implements irq_set_vcpu_affinity() hook to setup vapic mode for pass-through devices Suravee Suthikulpanit
2016-07-11 10:11 ` [PART2 PATCH v3 09/11] iommu/amd: Enable vAPIC interrupt remapping mode by default Suravee Suthikulpanit
2016-07-11 10:11 ` [PART2 PATCH v3 10/11] svm: Introduce AMD IOMMU avic_ga_log_notifier Suravee Suthikulpanit
2016-07-11 19:09   ` Radim Krčmář
2016-07-13  8:53     ` Suravee Suthikulpanit
2016-07-11 10:11 ` [PART2 PATCH v3 11/11] svm: Implements update_pi_irte hook to setup posted interrupt Suravee Suthikulpanit

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=20160711185943.GA1375@potion \
    --to=rkrcmar@redhat.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 \
    --cc=suravee.suthikulpanit@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