From: Alexander Popov <alex.popov@linux.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Marc Zyngier <marc.zyngier@arm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Dmitry Vyukov <dvyukov@google.com>,
Jiang Liu <jiang.liu@linux.intel.com>,
Jason Cooper <jason@lakedaemon.net>,
Radim Krcmar <rkrcmar@redhat.com>, Joerg Roedel <joro@8bytes.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
kvm@vger.kernel.org
Subject: Re: [PATCH 1/1] x86/apic: Introduce paravirq irq_domain
Date: Tue, 16 Aug 2016 23:00:53 +0300 [thread overview]
Message-ID: <ec1a1f29-ac61-0f3f-4d63-3ab26fa8bf67@linux.com> (raw)
In-Reply-To: <ea6a1ec8-1693-1511-8e34-a5d32c138b66@redhat.com>
On 15.08.2016 15:37, Paolo Bonzini wrote:
> On 15/08/2016 13:51, Alexander Popov wrote:
>> On 13.08.2016 09:20, Paolo Bonzini wrote:
>>> So just let the irqdomain know about your hypervisor and avoid the
>>> pointless indirection through function pointers, and only call
>>> arch_init_paravirq_domain in a file specific to your hypervisor.
>>
>> Paolo, I would like paravirq irq_domain to be useful for many hypervisors,
>> not only for one developed by Positive Technologies.
>
> If somebody else comes up with similar needs, leave the generalization
> of the code to them. The maintainers will surely remember. Without two
> users, there's a nonzero chance that the abstraction you have is not
> good enough, and actually gets in the way of the "second user".
Ok. I'll return with v2. Thank you.
Best regards,
Alexander
next prev parent reply other threads:[~2016-08-16 19:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 14:02 Alexander Popov
2016-08-11 16:44 ` Paolo Bonzini
2016-08-12 10:56 ` Alexander Popov
2016-08-12 11:43 ` Paolo Bonzini
2016-08-12 22:07 ` Alexander Popov
2016-08-13 6:20 ` Paolo Bonzini
2016-08-15 11:51 ` Alexander Popov
2016-08-15 12:37 ` Paolo Bonzini
2016-08-16 20:00 ` Alexander Popov [this message]
2016-08-17 14:36 ` Jan Kiszka
2016-08-17 22:58 ` Alexander Popov
2016-08-19 10:47 ` Jan Kiszka
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=ec1a1f29-ac61-0f3f-4d63-3ab26fa8bf67@linux.com \
--to=alex.popov@linux.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=jason@lakedaemon.net \
--cc=jiang.liu@linux.intel.com \
--cc=joro@8bytes.org \
--cc=keescook@chromium.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
Powered by JetHome