From: Alex Williamson <alex.williamson@hp.com>
To: "Duan, Ronghui" <ronghui.duan@intel.com>
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"Zhang, Xing Z" <xing.z.zhang@intel.com>,
"Xu, Anthony" <anthony.xu@intel.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>,
xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: RE: Re: free_irq_vector on ia64
Date: Tue, 04 Sep 2007 10:08:29 -0600 [thread overview]
Message-ID: <1188922109.6307.5.camel@lappy> (raw)
In-Reply-To: <82C666AA63DC75449C51EAD62E8B2BEC18391D@pdsmsx412.ccr.corp.intel.com>
On Mon, 2007-09-03 at 15:27 +0800, Duan, Ronghui wrote:
> Hi Alex:
>
> I follow your steps to hide e1000 from domain0, adding
> "pciback.hide==
> (0000:01:00.0)" in append line, then reboot .It seem that all right. The
> NAT consumption fault may have fixed by this patch:
> http://xenbits.xensource.com/xen-unstable.hg?rev/7158623a1b3d
>
> Could you please have a check?
That could be why I don't get a NaT consumption like the comment
indicated, but I still get the Oops. It doesn't seem like there's
anything platform specific here, so I'm not sure why you don't see it.
Note that I'm hiding function 1 of a two port, two function e1000, while
you're hiding function 0. I don't know if that matters, but perhaps a
variable to play with.
> BTW: It seems that we don't free irq_handler of e1000, so when
> rebooting, there may be some warning message printing in the serial
> port!
> Thank you!
Yup, that's a bug in our base 2.6.18 kernel which should go away next
time we re-base. However, that's a separate issue. Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
next prev parent reply other threads:[~2007-09-04 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 10:48 free_irq_vector on ia64 Herbert Xu
2007-08-30 14:34 ` Alex Williamson
2007-09-03 7:27 ` [Xen-devel] " Duan, Ronghui
2007-09-04 16:08 ` Alex Williamson [this message]
2007-09-04 19:44 ` Alex Williamson
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=1188922109.6307.5.camel@lappy \
--to=alex.williamson@hp.com \
--cc=anthony.xu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=ronghui.duan@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
--cc=xiantao.zhang@intel.com \
--cc=xing.z.zhang@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 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.