All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	John Byrne <john.l.byrne@hp.com>
Subject: Re: [PATCH] Allow blktap to build as a module
Date: Wed, 3 Jan 2007 12:45:17 +0000	[thread overview]
Message-ID: <20070103124517.GA3067@redhat.com> (raw)
In-Reply-To: <459B7A36.76E4.0078.0@novell.com>

On Wed, Jan 03, 2007 at 08:41:10AM +0000, Jan Beulich wrote:
> >>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 03.01.07 09:20 >>>
> >IIRC blktap doesn't straightforwardly build and work as a module. Some code
> >cleanup is required (getting rid of zap_page_range()?). There's no point in
> >taking the trivial Makefile fragment until that is fixed satisfactorily.
> 
> For the moment, we just leveraged the fact that in the SLE10 kernels
> zap_page_range() is being exported for other reasons. In 10.2, we added
> the export.

We did likewise for Fedora & RHEL - it was pretty trivial really to make
it work as a module.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2007-01-03 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03  0:58 [PATCH] Allow blktap to build as a module John Byrne
2007-01-03  8:12 ` Jan Beulich
2007-01-03  8:20   ` Keir Fraser
2007-01-03  8:41     ` Jan Beulich
2007-01-03 12:45       ` Daniel P. Berrange [this message]
2007-01-03 18:15     ` John Byrne

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=20070103124517.GA3067@redhat.com \
    --to=berrange@redhat.com \
    --cc=jbeulich@novell.com \
    --cc=john.l.byrne@hp.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.