[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] 2.6.30 dom0 Xen patches


  • To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Andrew Lyon <andrew.lyon@xxxxxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Fri, 17 Jul 2009 14:14:45 -0700 (PDT)
  • Cc: Jan Beulich <JBeulich@xxxxxxxxxx>
  • Delivery-date: Fri, 17 Jul 2009 14:15:16 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=gTsMr0bTadtqBeS8fgFwxwzu/V4JP+7r/8fA4oM5jF4Plc5AcNzMJATn9Wa8UvMGOFCpDb23R0MLXbYXjlY5bhQyqfimWLzQ9KA53fERiMczeMC4wTZtOMRoQN7LJGQOB0agzq+smcHt/Uq8dw/SKunkVEUOI+FZVkz54uMKw2I=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

  Seems to work nice Solaris 10 U7 (64-bit) HVM DomU  loads
pretty fast  with PV drivers at Xen 3.4.1-rc7 Ubuntu 9.04 Dom0 with
2.6.30.1 xenified via rebased patch set V.3
 
  I believe V.2 should be considered as deprecated due to recent message from Jan Beulich :-

>>> Boris Derzhavets <bderzhavets@xxxxxxxxx> 17.07.09 14:57 >>>
>Fix patch set before applying.

The second hunk is at best bogus: arch_probe_nr_irqs() only gets
referenced from a code section that's inside CONFIG_SPARSE_IRQ, and
when that option is selected, you'll have a duplicate symbol definition
issue between the arch_probe_nr_irqs() in arch/x86/kernel/apic/io_apic.c
and the one in drivers/xen/core/evtchn.c. Additionally, simply enabling
the function in arch/x86/kernel/apic/io_apic.c does not do, as it may
leave you with insufficient space for dynamic IRQs (which is why I
cloned it into a properly working function in drivers/xen/core/evtchn.c).

Jan

--- On Fri, 7/17/09, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:

From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Subject: Re: [Xen-devel] 2.6.30 dom0 Xen patches
To: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Cc: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Friday, July 17, 2009, 2:11 PM

> As I don't expect to get the stuff I have pushed out before our tree gets
> switched to 2.6.31-rc, I'll attach the whole patch set as it is after fixing the
> !ia32-emulation problem you pointed out.

I have rebased the 2.6.30 Xen patches
(xen-patches-2.6.30-20090703.tb2) that Jan Beulich was kind enough to
send to me before openSUSE switch their tree to 2.6.31-git etc, the
new files are available at
http://code.google.com/p/gentoo-xen-kernel/downloads/list

xen-sources-2.6.30-r2.ebuild
xen-patches-2.6.30-3.tar.bz2

Non-Gentoo users can simply apply the patches to 2.6.30.1 in numeric order.

As usual I did not include patches that are for backwards
compatibility, suse specific features, experimental features (eg
tmem), or that require patches to Xen itself.

Note that James Harper's gplpv driver for networking (xennet.sys) does
not work with 2.6.30, he has given me a patch which works around the
problem but you will need to recompile the drivers yourself, the patch
is:

diff -r 36221c314d54 xennet/xennet_common.c
--- a/xennet/xennet_common.c    Wed Jul 15 20:05:36 2009 +1000
+++ b/xennet/xennet_common.c    Fri Jul 17 23:53:12 2009 +1000
@@ -181,6 +181,12 @@
      return PARSE_TOO_SMALL;
          }
            }
            +
            +  if ((ULONG)XN_HDR_SIZE + pi->ip4_length > pi->total_length)
            +  {
            +    KdPrint((__DRIVER_NAME "     XN_HDR_SIZE + ip4_length
(%d) > total_length (%d)\n", XN_HDR_SIZE + pi->ip4_length,
pi->total_length));
            +    return PARSE_UNKNOWN_TYPE;
            +  }

              pi->tcp_length = pi->ip4_length - pi->ip4_header_length
- pi->tcp_header_length;
                pi->tcp_remaining = pi->tcp_length;


Andy

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.