From: Ian Campbell <Ian.Campbell@XenSource.com>
To: Doi.Tsunehisa@jp.fujitsu.com
Cc: xen-devel@lists.xensource.com,
Kasai Takanori <kasai.takanori@jp.fujitsu.com>,
xen-ia64-devel@lists.xensource.com
Subject: Re: [PATCH][RESEND] PV drivers for HVM guests
Date: Fri, 27 Oct 2006 10:40:18 +0100 [thread overview]
Message-ID: <1161942018.13318.49.camel@localhost.localdomain> (raw)
In-Reply-To: <200610270411.k9R4BrF06900@photon.sky.yk.fujitsu.co.jp>
On Fri, 2006-10-27 at 13:11 +0900, Doi.Tsunehisa@jp.fujitsu.com wrote:
> Takanori (he is my co-worker) checked this patch, but it occures
> compile error in linux-xen. We are investigating it.
Thanks, I'll reply to him in a moment.
> >> BTW, I might find a issue about NET_IP_ALIGN in the compatible shim.
> >> Currentry, its value is 0, but the value should be matched a value of
> >> netback module. Thus, its value should be 2, I think.
> >>
> >> What do you think about the issue ?
> >
> > My thinking was that since those older kernels don't define NET_IP_ALIGN
> > and don't hardcode the number 2 anywhere they don't expect any extra
> > alignment. Therefore using 0 seems correct in terms of behaving the same
> > as native drivers do on those versions. I'm not sure I would want to
> > backport the addition of the extra padding in our drivers, the distros
> > haven't seen the need for example...
>
> Hmm, I thought that NET_IF_ALIGN mismatch between netfront and netback
> occures a confusion of VNIF. But I might be imagining if it was used
> correctly.
I'd not heard about or seen that problem. Lets leave things as they are
and if a problem arises we'll revisit it.
> Is it used on SLES9 guest ? I don't have the environment.
Yes, I'm compile testing against SLES9sp3 (2.6.5 based) and RHEL4 update
4 (2.6.9 based) kernels. I don't have an IA64 platform to do anything
more than that.
Ian.
next prev parent reply other threads:[~2006-10-27 9:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 13:51 [PATCH][RESEND] PV drivers for HVM guests Ky Srinivasan
2006-10-18 23:56 ` Doi.Tsunehisa
2006-10-19 13:53 ` Ky Srinivasan
2006-10-20 10:12 ` Doi.Tsunehisa
2006-10-20 13:54 ` Ky Srinivasan
2006-10-23 1:45 ` Doi.Tsunehisa
2006-10-24 2:54 ` DOI Tsunehisa
2006-10-24 15:26 ` Ian Campbell
2006-10-24 23:54 ` Doi.Tsunehisa
2006-10-25 3:11 ` Doi.Tsunehisa
2006-10-25 11:03 ` Ian Campbell
2006-10-26 0:13 ` Doi.Tsunehisa
2006-10-26 3:58 ` Doi.Tsunehisa
2006-10-26 6:37 ` Doi.Tsunehisa
2006-10-26 14:15 ` Ian Campbell
2006-10-27 4:11 ` [Xen-devel][PATCH][RESEND] " Doi.Tsunehisa
2006-10-27 9:40 ` Ian Campbell [this message]
[not found] ` <00a201c6f96a$811feac0$dab2220a@VF03007L>
[not found] ` <1161943070.13318.53.camel@localhost.localdomain>
2006-10-27 11:43 ` [PATCH][RESEND] " Kasai Takanori
[not found] ` <03b301c6fa5a$8cc725a0$dab2220a@VF03007L>
2006-11-01 23:55 ` [PATCH][RESEND] PV drivers for HVMguests Kasai Takanori
2006-11-02 10:01 ` Ian Campbell
2006-10-25 11:03 ` [PATCH][RESEND] PV drivers for HVM guests Ian Campbell
2006-10-26 0:16 ` Doi.Tsunehisa
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=1161942018.13318.49.camel@localhost.localdomain \
--to=ian.campbell@xensource.com \
--cc=Doi.Tsunehisa@jp.fujitsu.com \
--cc=kasai.takanori@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-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 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.