linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-next@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>,
	virtio-dev@lists.oasis-open.org,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: mmotm 2014-03-10-15-35 uploaded (virtio_balloon)
Date: Tue, 11 Mar 2014 14:40:14 -0700	[thread overview]
Message-ID: <20140311214014.GA18708@leaf> (raw)
In-Reply-To: <20140311123133.f40adf3154452e82aecb61ca@linux-foundation.org>

On Tue, Mar 11, 2014 at 12:31:33PM -0700, Andrew Morton wrote:
> On Tue, 11 Mar 2014 12:20:46 -0700 Josh Triplett <josh@joshtriplett.org> wrote:
> 
> > > > ERROR: "balloon_devinfo_alloc" [drivers/virtio/virtio_balloon.ko] undefined!
> > > > ERROR: "balloon_page_enqueue" [drivers/virtio/virtio_balloon.ko] undefined!
> > > > ERROR: "balloon_page_dequeue" [drivers/virtio/virtio_balloon.ko] undefined!
> > > > 
> > > > when loadable module
> > > > 
> > > > or
> > > > 
> > > > virtio_balloon.c:(.text+0x1fa26): undefined reference to `balloon_page_enqueue'
> > > > virtio_balloon.c:(.text+0x1fb87): undefined reference to `balloon_page_dequeue'
> > > > virtio_balloon.c:(.text+0x1fdf1): undefined reference to `balloon_devinfo_alloc'
> > > > 
> > > > when builtin.
> > > 
> > > OK, thanks, I'll drop
> > > http://ozlabs.org/~akpm/mmots/broken-out/mm-disable-mm-balloon_compactionc-completely-when-config_balloon_compaction.patch
> > 
> > Sorry about that; I missed that case in my testing.  It always seems
> > strange that the dependency goes that way around.
> > 
> > With virtio-balloon being the one and only user of this API, would it be
> > reasonable to just only compile in balloon_compaction.o when
> > CONFIG_VIRTIO_BALLOON?
> 
> Better to make VIRTIO_BALLOON depend on (or select) BALLOON_COMPACTION.

I'd love to do that, but as far as I can tell, VIRTIO_BALLOON has gone
out of its way to support !CONFIG_BALLOON_COMPACTION.

Could someone who works on VIRTIO_BALLOON provide some details here
about the distinction?

- Josh Triplett

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2014-03-11 21:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 22:37 mmotm 2014-03-10-15-35 uploaded akpm
2014-03-11 17:04 ` mmotm 2014-03-10-15-35 uploaded (media/pci/ttpci/av7110) Randy Dunlap
2014-03-11 17:12 ` mmotm 2014-03-10-15-35 uploaded (virtio_balloon) Randy Dunlap
2014-03-11 18:03   ` Andrew Morton
2014-03-11 19:20     ` Josh Triplett
2014-03-11 19:31       ` Andrew Morton
2014-03-11 21:40         ` Josh Triplett [this message]
2014-03-17  3:32           ` Rusty Russell

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=20140311214014.GA18708@leaf \
    --to=josh@joshtriplett.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=rusty@rustcorp.com.au \
    --cc=virtio-dev@lists.oasis-open.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;
as well as URLs for NNTP newsgroup(s).