From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Bruce Edge <bruce.edge@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: pv-ops domU not working with MSI interrupts on Nehalem
Date: Wed, 6 Oct 2010 10:21:57 -0400 [thread overview]
Message-ID: <20101006142157.GA1590@dumpdata.com> (raw)
In-Reply-To: <AANLkTim7RceMqdnj0wxvTUWHTtSEtGptSs+oFHurM9BA@mail.gmail.com>
On Tue, Oct 05, 2010 at 11:21:38AM -0700, Bruce Edge wrote:
> On Mon, Oct 4, 2010 at 7:48 AM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> >> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git ?
> >>
> >> Your devel/xen-pcifront-0.7 isn't visible:
> >
> > It should be now. I pushed it late on Friday and repushed it today since it had
> > some commits with the wrong committer field.
> >
>
> Is there anything special one needs to do when building this kernel?
Wow. I've never seen those errors before. Can you send me your .config file
so I can make sure this does not happend
For me, I've these options defined:
[konrad@tst002 bootstrap]$ cat linux-build/.config|grep XEN
CONFIG_XEN=y
CONFIG_XEN_PVHVM=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=8
CONFIG_XEN_SAVE_RESTORE=y
CONFIG_XEN_DEBUG_FS=y
CONFIG_PCI_XEN=y
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_XEN_BLKDEV_FRONTEND=m
# CONFIG_NETXEN_NIC is not set
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_XEN_KBDDEV_FRONTEND=m
CONFIG_HVC_XEN=y
CONFIG_XEN_FBDEV_FRONTEND=m
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XENFS=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_PLATFORM_PCI=m
CONFIG_SWIOTLB_XEN=y
next prev parent reply other threads:[~2010-10-06 14:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 15:52 pv-ops domU not working with MSI interrupts on Nehalem Bruce Edge
2010-09-27 17:24 ` Konrad Rzeszutek Wilk
2010-09-27 19:16 ` Bruce Edge
2010-09-27 19:54 ` Konrad Rzeszutek Wilk
2010-09-27 23:54 ` Bruce Edge
2010-09-28 1:15 ` Jiang, Yunhong
2010-09-28 3:16 ` Bruce Edge
2010-09-28 3:26 ` Jiang, Yunhong
2010-09-28 4:45 ` Bruce Edge
2010-09-28 16:08 ` Lin, Ray
2010-09-28 16:19 ` Konrad Rzeszutek Wilk
2010-09-28 18:35 ` Lin, Ray
2010-09-28 20:14 ` Konrad Rzeszutek Wilk
2010-09-28 20:38 ` Lin, Ray
2010-09-29 0:53 ` Jiang, Yunhong
2010-09-30 16:30 ` Lin, Ray
2010-09-28 14:56 ` Konrad Rzeszutek Wilk
2010-09-30 18:55 ` Bruce Edge
2010-10-01 21:11 ` Konrad Rzeszutek Wilk
2010-10-01 21:19 ` Bruce Edge
2010-10-01 23:30 ` Bruce Edge
2010-10-03 5:46 ` Bruce Edge
2010-10-03 12:08 ` Pasi Kärkkäinen
2010-10-04 14:48 ` Konrad Rzeszutek Wilk
2010-10-05 18:21 ` Bruce Edge
2010-10-06 14:21 ` Konrad Rzeszutek Wilk [this message]
2010-10-06 18:21 ` Bruce Edge
2010-10-08 16:48 ` Lin, Ray
2010-10-08 17:30 ` Konrad Rzeszutek Wilk
2010-10-08 17:40 ` Lin, Ray
2010-10-08 17:52 ` Bruce Edge
2010-10-08 21:01 ` Lin, Ray
2010-10-08 17:56 ` Bruce Edge
2010-10-11 21:12 ` Bruce Edge
2010-10-11 21:46 ` Konrad Rzeszutek Wilk
2010-10-13 21:36 ` Bruce Edge
2010-10-13 21:46 ` Konrad Rzeszutek Wilk
2010-10-13 22:00 ` Bruce Edge
2010-10-13 22:08 ` Bruce Edge
2010-10-14 13:57 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2010-09-28 23:25 Lin, Ray
2010-09-28 23:57 ` 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=20101006142157.GA1590@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=bruce.edge@gmail.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 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).