xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	xen-devel@lists.xensource.com, konrad@kernel.org
Subject: Re: [PATCH v6] xen pci backend driver.
Date: Mon, 25 Apr 2011 11:58:50 -0700	[thread overview]
Message-ID: <20110425115850.48b7d254@jbarnes-desktop> (raw)
In-Reply-To: <1303333640-5994-1-git-send-email-konrad.wilk@oracle.com>

On Wed, 20 Apr 2011 17:07:19 -0400
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:

> The following patch implements the Xen pci backend for upstream Linux.
> This is the host side counterpart to the frontend driver in
> drivers/pci/xen-pcifront.c. The PV protocol is also implemented by
> frontend drivers in other OSes too, such as the BSDs.
> 
> This driver has a long history as an out of tree driver but I am
> submitting it here as a single monolithic patch to aid review. Once it
> has been reviewed and is considered suitable for merging can we perhaps
> consider merging the equivalent git branch which maintains much of
> history?

It looks pretty clean at first glance (though 128k worth of patch isn't
an ideal way to split it).

But maybe the back end belongs in arch/x86/xen as it's really a arch
specific PCI implementation at heart?  I don't want to be a bottleneck
for any Xen specific PCI patches in the future, and other arches have a
similar split (though not always with an ideal core vs arch split).

Figuring out some way to preserve the git history is probably a good
idea, assuming it's not too much of a mess.  If it is, a more
reasonable split and history using rebase could probably be contrived
before merging it.

-- 
Jesse Barnes, Intel Open Source Technology Center

  parent reply	other threads:[~2011-04-25 18:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 21:07 [PATCH v6] xen pci backend driver Konrad Rzeszutek Wilk
2011-04-20 21:07 ` [PATCH] " Konrad Rzeszutek Wilk
2011-04-25 18:58 ` Jesse Barnes [this message]
2011-04-26  3:05   ` [Xen-devel] Re: [PATCH v6] " Konrad Rzeszutek Wilk
2011-05-27 15:22   ` Konrad Rzeszutek Wilk
2011-05-28 14:18     ` Fix wrong memory size of nested shadow_io_bitmap Dong, Eddie
2011-05-31 17:00     ` [Xen-devel] Re: [PATCH v6] xen pci backend driver Jesse Barnes
2011-07-15 15:37       ` Konrad Rzeszutek Wilk

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=20110425115850.48b7d254@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=konrad.wilk@oracle.com \
    --cc=konrad@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).