From: Kieran Mansley <kmansley@solarflare.com>
To: "Zhao, Yunfeng" <yunfeng.zhao@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: compile error of HVM pv drivers
Date: Mon, 30 Jul 2007 15:54:56 +0100 [thread overview]
Message-ID: <1185807296.31234.4.camel@moonstone.uk.level5networks.com> (raw)
In-Reply-To: <1185806843.31234.3.camel@moonstone.uk.level5networks.com>
On Mon, 2007-07-30 at 15:47 +0100, Kieran Mansley wrote:
> On Mon, 2007-07-30 at 22:39 +0800, Zhao, Yunfeng wrote:
> > Hi, Kieran
> > I just checked 2.6.16 kernel source.
> > netif_tx_lock_bh is not in the code of 2.6.16, but it is in 2.6.18
>
> In that case replacing the calls (there are two in that file) to
> netif_tx_lock_bh() with:
>
> spin_lock_bh(&vif_state->np->netdev->xmit_lock);
>
> And similarly the calls to netif_tx_unlock_bh() with spin_unlock_bh(),
> may solve your problem.
In light of Keir's reply pointing out the compat definition of
netif_tx_lock_bh() this is clearly not going to help. Sorry. I thought
it was an odd way of the compiler to express that error.
Kieran
prev parent reply other threads:[~2007-07-30 14:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 9:28 compile error of HVM pv drivers Zhao, Yunfeng
2007-07-30 9:52 ` Keir Fraser
2007-07-30 9:58 ` Kieran Mansley
2007-07-30 10:13 ` Mats Petersson
2007-07-30 12:43 ` Zhao, Yunfeng
2007-07-30 13:42 ` Kieran Mansley
2007-07-30 13:49 ` Zhao, Yunfeng
2007-07-30 14:05 ` Kieran Mansley
2007-07-30 14:15 ` Zhao, Yunfeng
2007-07-30 14:22 ` Zhao, Yunfeng
2007-07-30 14:24 ` Kieran Mansley
2007-07-30 14:32 ` Zhao, Yunfeng
2007-07-30 14:39 ` Zhao, Yunfeng
2007-07-30 14:42 ` Keir Fraser
2007-07-30 14:47 ` Kieran Mansley
2007-07-30 14:51 ` Keir Fraser
2007-07-30 15:02 ` Zhao, Yunfeng
2007-07-30 15:05 ` Keir Fraser
2007-07-30 15:38 ` Zhao, Yunfeng
2007-07-30 15:42 ` Kieran Mansley
2007-07-30 16:42 ` Keir Fraser
2007-07-30 14:54 ` Kieran Mansley [this message]
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=1185807296.31234.4.camel@moonstone.uk.level5networks.com \
--to=kmansley@solarflare.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunfeng.zhao@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.