All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH 0 of 5] PV on HVM Xen
Date: Wed, 17 Mar 2010 15:21:08 +0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1003171047230.23661@kaball-desktop> (raw)
In-Reply-To: <201003171738.37830.sheng@linux.intel.com>

On Wed, 17 Mar 2010, Sheng Yang wrote:
> I would like to work on the PIRQ porting upstream Linux

I am glad to hear that!


> A simple version would be just using PIRQ instead of VIRQ in my 
> patches, but PIRQ is flexible, I would see if I can do more with it

After the first part of your series gets applied, I'll rebase my pirq
remapping patches on top of it, then you can tell me what's wrong so I
can change it. I am very open to critics or suggestions.
I would also prefer that you take my pirq remapping patches, you make
any change you like, then you send your work to the list, rather than
reinventing the wheel.
I value your contributions so I would be happy if you could work on my
series, that even though is working still misses MSI support and I am
sure you'll be able to make many other important improvements.


> And we may not get a version exactly the same as pv_ops dom0 code in
> the end... I would try to make them similar and make the HVM part
> small enough, then reduce Jeremy's maintain effort.
> 

As pointed out before by Jeremy and Konrad, the best starting point is
probably Konrad's pv/pcifront-2.6.31 tree: it contains most of the pirq
stuff, ready to be upstreamed.
AFAICT the only things required to make pirq mappings work (as in
my series) that are missing are:

- xen_register_gsi

- xen_setup_pirqs

- the xen_register_gsi hook in acpi_register_gsi

the first two should be easy to port because they don't require any
change but the last one definitely needs modifications in order to be
accepted upstream.
I didn't include MSI support because is not required, but that is
another area that needs changes.

  parent reply	other threads:[~2010-03-17 15:21 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 15:46 [PATCH 0 of 5] PV on HVM Xen Stefano Stabellini
2010-03-10 17:33 ` [Xen-devel] " Pasi Kärkkäinen
2010-03-10 17:55   ` Stefano Stabellini
2010-03-10 19:45     ` Jeremy Fitzhardinge
2010-03-12  3:23 ` Sheng Yang
2010-03-12  3:23   ` Sheng Yang
2010-03-12 10:42   ` [Xen-devel] " Stefano Stabellini
2010-03-12 16:00     ` Stefano Stabellini
2010-03-15  4:05       ` Sheng Yang
2010-03-15  8:29         ` Sheng Yang
2010-03-15 12:22           ` Stefano Stabellini
2010-03-17  9:38             ` Sheng Yang
2010-03-17 14:18               ` Konrad Rzeszutek Wilk
2010-03-17 15:21               ` Stefano Stabellini [this message]
2010-03-17 16:13                 ` Jeremy Fitzhardinge
2010-03-18  1:30                   ` Sheng Yang
2010-03-19 20:38                     ` Jeremy Fitzhardinge
2010-03-22  6:26                       ` MSI proposal and work transfer...(was: Re: [PATCH 0 of 5] PV on HVM Xen) Sheng Yang
2010-03-23 20:47                         ` Jeremy Fitzhardinge
2010-03-24  8:19                           ` Sheng Yang
2010-03-23 23:16                         ` Stefano Stabellini
2010-03-24  8:25                           ` Sheng Yang
2010-03-18  2:19                 ` [PATCH 0 of 5] PV on HVM Xen Sheng Yang
2010-03-18 16:42                   ` Jeremy Fitzhardinge
2010-03-17 16:13               ` Jeremy Fitzhardinge
2010-03-15 12:28         ` Stefano Stabellini
2010-03-15 23:08           ` Jeremy Fitzhardinge
2010-03-15 23:24             ` Frank van der Linden
2010-03-16  0:32             ` Dan Magenheimer
2010-03-16  6:09               ` Sheng Yang
2010-03-16 16:46                 ` Dan Magenheimer
2010-03-16 11:07             ` Stefano Stabellini
2010-03-16 17:23               ` Jeremy Fitzhardinge
2010-03-16 17:32                 ` Stefano Stabellini
2010-03-16 17:41                   ` Jeremy Fitzhardinge
2010-03-16 18:06                     ` Stefano Stabellini
2010-03-16 18:26                       ` Jeremy Fitzhardinge
2010-03-16 18:37                         ` Stefano Stabellini
2010-03-17  8:51                           ` Sheng Yang
2010-03-17  9:18                             ` Sheng Yang
2010-03-17 15:17                               ` Stefano Stabellini
2010-03-17 18:20                                 ` Ian Campbell
2010-03-18  1:42                                   ` Sheng Yang
2010-03-18  1:35                                 ` Sheng Yang
2010-03-18 14:22                                   ` Stefano Stabellini
2010-03-18 16:50                                     ` Jeremy Fitzhardinge
2010-03-18 17:30                                 ` Jeremy Fitzhardinge
2010-03-12 21:53     ` [Xen-devel] " Jeremy Fitzhardinge
2010-03-12 11:44 Boris Derzhavets
2010-03-12 11:59 ` Stefano Stabellini
2010-03-12 15:01   ` Boris Derzhavets
2010-03-12 15:08     ` Stefano Stabellini
2010-03-12 15:09       ` Boris Derzhavets
2010-03-12 20:10     ` Jeremy Fitzhardinge
2010-03-12 21:14       ` Boris Derzhavets
2010-03-12 21:22         ` Jeremy Fitzhardinge
2010-03-12 21:28           ` Boris Derzhavets
2010-03-12 21:25       ` Boris Derzhavets
2010-03-12 21:29         ` Jeremy Fitzhardinge
2010-03-12 22:08           ` Boris Derzhavets
2010-03-12 22:11             ` Jeremy Fitzhardinge
2010-03-12 22:13               ` Boris Derzhavets
2010-03-12 22:22                 ` Jeremy Fitzhardinge
2010-03-15 15:53                   ` Stefano Stabellini
2010-03-15 16:02                     ` Boris Derzhavets
2010-03-15 17:27                   ` Stefano Stabellini
2010-03-15 17:49                     ` Boris Derzhavets
2010-03-15 18:01                       ` Stefano Stabellini

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.DEB.2.00.1003171047230.23661@kaball-desktop \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=jeremy@goop.org \
    --cc=sheng@linux.intel.com \
    --cc=xen-devel@lists.xensource.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.