From: Eric Auger <eric.auger@linaro.org>
To: Pavel Fedin <p.fedin@samsung.com>,
'Paolo Bonzini' <pbonzini@redhat.com>,
'Andre Przywara' <andre.przywara@arm.com>
Cc: kvm@vger.kernel.org, 'Gleb Natapov' <gleb@kernel.org>,
'Jan Kiszka' <jan.kiszka@siemens.com>,
'Marcelo Tosatti' <mtosatti@redhat.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: Extensions for KVM MSI related ioctls
Date: Mon, 13 Jul 2015 16:24:23 +0200 [thread overview]
Message-ID: <55A3CA17.1010500@linaro.org> (raw)
In-Reply-To: <03b901d0bd70$6c2f4b50$448de1f0$@samsung.com>
On 07/13/2015 03:32 PM, Pavel Fedin wrote:
> Hello!
>
>> I think I prefer the flag. Offhand it sounds easier to add support for
>> it to non-ARM architectures, compared to KVM_IRQ_ROUTING_EXTENDED_MSI.
>
> Actually i also voted for flag, because it is already introduced in (2), and i'm not a fan of
> adding new definitions where we can reuse existing ones. IMHO using flag would make an API more
> consistent.
OK I will respin with user space flag.
Andre, what about the kernel routing entry struct. You wanted me to get
rid of KVM_IRQ_ROUTING_EXTENDED_MSI there too. Will you be able to
manage a usespace wrong setting if the type is not set?
Best Regards
Eric
>
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
>
>
WARNING: multiple messages have this Message-ID (diff)
From: eric.auger@linaro.org (Eric Auger)
To: linux-arm-kernel@lists.infradead.org
Subject: Extensions for KVM MSI related ioctls
Date: Mon, 13 Jul 2015 16:24:23 +0200 [thread overview]
Message-ID: <55A3CA17.1010500@linaro.org> (raw)
In-Reply-To: <03b901d0bd70$6c2f4b50$448de1f0$@samsung.com>
On 07/13/2015 03:32 PM, Pavel Fedin wrote:
> Hello!
>
>> I think I prefer the flag. Offhand it sounds easier to add support for
>> it to non-ARM architectures, compared to KVM_IRQ_ROUTING_EXTENDED_MSI.
>
> Actually i also voted for flag, because it is already introduced in (2), and i'm not a fan of
> adding new definitions where we can reuse existing ones. IMHO using flag would make an API more
> consistent.
OK I will respin with user space flag.
Andre, what about the kernel routing entry struct. You wanted me to get
rid of KVM_IRQ_ROUTING_EXTENDED_MSI there too. Will you be able to
manage a usespace wrong setting if the type is not set?
Best Regards
Eric
>
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
>
>
next prev parent reply other threads:[~2015-07-13 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 10:25 Extensions for KVM MSI related ioctls Andre Przywara
2015-07-13 10:25 ` Andre Przywara
2015-07-13 12:35 ` Paolo Bonzini
2015-07-13 12:35 ` Paolo Bonzini
2015-07-13 13:32 ` Pavel Fedin
2015-07-13 13:32 ` Pavel Fedin
2015-07-13 14:24 ` Eric Auger [this message]
2015-07-13 14:24 ` Eric Auger
2015-07-13 14:29 ` Andre Przywara
2015-07-13 14:29 ` Andre Przywara
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=55A3CA17.1010500@linaro.org \
--to=eric.auger@linaro.org \
--cc=andre.przywara@arm.com \
--cc=gleb@kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mtosatti@redhat.com \
--cc=p.fedin@samsung.com \
--cc=pbonzini@redhat.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.