From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: kvm@vger.kernel.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] module_refcounting and anonymous inodes
Date: Tue, 09 Dec 2008 11:51:07 +0200 [thread overview]
Message-ID: <493E3F8B.7070603@redhat.com> (raw)
In-Reply-To: <200812091743.26586.sheng@linux.intel.com>
Sheng Yang wrote:
> Should we push the first patch to 2.6.28?
It's not a recent regression, so no.
> I got some trouble with the separate
> 2nd patch, for I am using Linus' tree and make KVM as modules, so the
> reference count reduced to negative now... (Oh Avi, I know you suggest to use
> in kernel rather than modules, but module is indeed convenient. :) )
>
Right, that would affect everyone. What we need is to hack the second
patch for external modules on <2.6.29.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-12-09 9:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 10:14 [PATCH 0/2] module_refcounting and anonymous inodes Christian Borntraeger
2008-12-02 10:16 ` [PATCH 1/2] anon_inodes: use fops->owner for module refcount Christian Borntraeger
2008-12-02 10:17 ` [PATCH 2/2] kvm: set owner of cpu and vm file operations Christian Borntraeger
2008-12-08 11:51 ` [PATCH 0/2] module_refcounting and anonymous inodes Christian Borntraeger
2008-12-08 11:57 ` Avi Kivity
2008-12-09 9:43 ` Sheng Yang
2008-12-09 9:51 ` Avi Kivity [this message]
2008-12-09 10:08 ` Christian Borntraeger
2008-12-09 10:15 ` Avi Kivity
2008-12-09 13:22 ` Avi Kivity
2008-12-10 2:05 ` Sheng Yang
2008-12-10 9:12 ` Avi Kivity
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=493E3F8B.7070603@redhat.com \
--to=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sheng@linux.intel.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).