public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	linux-kernel@vger.kernel.org, dwmw2@infradead.org,
	avi@qumranet.com, kvm@vger.kernel.org, "Williams,
	Dan J" <dan.j.williams@intel.com>
Subject: Re: mmotm 2008-09-22-01-36 uploaded (kvm)
Date: Mon, 22 Sep 2008 14:58:52 -0700	[thread overview]
Message-ID: <200809221458.53192.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080922125227.2b837457.akpm@linux-foundation.org>

On Monday, September 22, 2008 12:52 pm Andrew Morton wrote:
> On Mon, 22 Sep 2008 11:19:47 -0700
>
> Randy Dunlap <randy.dunlap@oracle.com> wrote:
> > On Mon, 22 Sep 2008 01:38:58 -0700 akpm@linux-foundation.org wrote:
> > > The mm-of-the-moment snapshot 2008-09-22-01-36 has been uploaded to
> > >
> > >    http://userweb.kernel.org/~akpm/mmotm/
> > >
> > > It contains the following patches against 2.6.27-rc7:
> >
> > ERROR: "intel_iommu_found" [arch/x86/kvm/kvm.ko] undefined!
> >
> > when CONFIG_DMAR=n.
>
> Yes, I got that too.  i386 allmodconfig fails similarly.  It's still
> unclear which tree in linux-next broke it.  PCI or async_tx, perhaps.

I don't have that symbol in my tree (yet).  It's part of one of the IOMMU KVM 
patch sets that's currently in-flight.  I'll add it to my linux-next tree 
today or tomorrow, assuming I get an ack from David about it (I'll bounce it 
over to him now).

Thanks,
Jesse

  reply	other threads:[~2008-09-22 21:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200809220838.m8M8cwC2031790@imap1.linux-foundation.org>
2008-09-22 18:19 ` mmotm 2008-09-22-01-36 uploaded (kvm) Randy Dunlap
2008-09-22 19:52   ` Andrew Morton
2008-09-22 21:58     ` Jesse Barnes [this message]
2008-09-22 21:59       ` Jesse Barnes
2008-09-22 22:10       ` Andrew Morton
2008-09-23  6:32         ` Amit Shah
2008-09-23 10:25           ` 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=200809221458.53192.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=akpm@linux-foundation.org \
    --cc=avi@qumranet.com \
    --cc=dan.j.williams@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.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