mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: KY Srinivasan <kys@microsoft.com>
Cc: "gregkh@suse.de" <gregkh@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Hank Janssen <hjanssen@microsoft.com>
Subject: RE: [PATCH]: Staging: hv: Allocate the vmbus irq dynamically
Date: Mon, 21 Feb 2011 15:51:56 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1102211549340.2701@localhost6.localdomain6> (raw)
In-Reply-To: <6E21E5352C11B742B20C142EB499E048013C67@TK5EX14MBXC128.redmond.corp.microsoft.com>

On Mon, 21 Feb 2011, KY Srinivasan wrote:
> > > > There are various ways to solve that proper.
> > > >
> > > >  - You can provide the interrupt number from ACPI/PCI or whatever your HV
> > > >    provides as enumeration.
> > > >
> > > >  - Use a fixed vector like XEN does for the event channel
> > > >
> > > >  - Use dynamic allocation in the IOAPIC space like the kernel does for
> > > >    MSI(-X)
> > > >
> > > > Thanks,
> > > >
> > > > 	tglx
> > >
> > > I am not claiming that what I have done here is the best possible solution.
> > > However, I will submit to you that it is better than what we had here
> > > prior to this patch.  I will address this and a  whole lot of other issues
> > > in future patches.
> > 
> > No, it's _NOT_ better in any way. You trade breaking your PV thing
> > against breaking random other drivers. Care to explain why you think
> > that's better ?
> 
> The root device for the VM is bound to the PV driver on some distributions.
> So, if we cannot load the PV drivers, we do not have a system that boots.
> In general, the system performance without these PV drivers is so poor that
> for all practical purposes, having the PV drivers is almost a requirement
> for having a useable system. While the platform supports configuration of the VM with
> some emulated devices, it is not a recommended configuration (because of
> performance reasons) for Linux virtual machines on the Hyper-V platform.

It does not matter whether it's recommended or not. If it results in a
non usable emulated device it's broken. Just imagine you grab the
serial interrupt, which results in not having a debug console. Not at
all acceptable.
 
> I have spent significantly more time debating this patch than
> developing this patch that I still think improves the current
> driver. I will leave it to Greg and other powers that be to decide
> if this patch will be accepted. Let me know what your verdict is.

As I said, any other clean solution (and I pointed out 3) over this
hack.

Thanks,

	tglx

  reply	other threads:[~2011-02-21 14:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 19:55 K. Y. Srinivasan
2011-02-18 21:14 ` Greg KH
2011-02-18 22:00   ` KY Srinivasan
2011-02-18 22:07     ` Greg KH
2011-02-18 22:16       ` KY Srinivasan
2011-02-18 22:29         ` Greg KH
2011-02-19  0:56           ` KY Srinivasan
2011-02-19  1:02             ` Greg KH
2011-02-19  1:19               ` KY Srinivasan
2011-02-19 10:23 ` Thomas Gleixner
2011-02-19 14:34   ` KY Srinivasan
2011-02-19 15:12     ` Thomas Gleixner
2011-02-19 16:46       ` KY Srinivasan
2011-02-20 16:15         ` Thomas Gleixner
2011-02-21  3:43           ` KY Srinivasan
2011-02-21  3:50             ` Greg KH
2011-02-21 11:02             ` Thomas Gleixner
2011-02-21 14:40               ` KY Srinivasan
2011-02-21 14:51                 ` Thomas Gleixner [this message]
2011-02-21 15:43                   ` Greg KH
2011-02-23 19:16                   ` Greg KH
2011-02-23 19:22                     ` KY Srinivasan
  -- strict thread matches above, loose matches on Subject: below --
2011-02-19  1:26 K. Y. Srinivasan
2011-02-15 15:15 [PATCH ]:Staging: " K. Y. Srinivasan
2011-02-15 15:59 ` Greg KH
2011-02-15 16:53   ` KY Srinivasan
2011-02-15 16:59     ` Hank Janssen
2011-02-15 17:22       ` Greg KH
2011-02-15 17:28         ` Hank Janssen
2011-02-15 19:09         ` Hank Janssen
2011-02-15 19:33           ` Greg KH
2011-02-15 17:25     ` Greg KH

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=alpine.LFD.2.00.1102211549340.2701@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@suse.de \
    --cc=haiyangz@microsoft.com \
    --cc=hjanssen@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.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

all inboxes | Powered by JetHome®