DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:content-type:date:message-id:mime-version:x-mailer
         :content-transfer-encoding;
        b=QSCa3lGDYLpM4YuoOMvgamboAufNtsfZdtd0eK1Z8TeCI1gZ1tdX2p7RlIrvbfnvI5
         wr9EOA4xLGmCydyoRTIiiJnzc+AR7sX5KML4owM5FU5iul4EkDOjsZ/1QHbhRYHCCKn8
         EQ3LBzH5dAeBRsEDzfDxbQQgMUuhTI6VEEpJs=
Subject: [alpine-devel] xen support in default kernel
From: Natanael Copa <natanael.copa@gmail.com>
To: Alpine-devel <alpine-devel@lists.alpinelinux.org>
Content-Type: text/plain
Date: Mon, 06 Apr 2009 16:32:37 +0200
Message-Id: <1239028357.26439.24.camel@nc>
Precedence: list
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

The default kernel (named linux-grsec in 1.9.x) have paravirt enabled. A
user here asked for xen support too which is not there currently.

The problem is that this requires that kernel is compiled for i586. We
currently do 486.

IIRC there was some newer cpus (found in TU-40?) that basicly is a
faster 486 CPU.

So, the question is, should we say that i596 is required for default
kernel, and support xen paravirtualization by default? Or should we make
a separate xenlinux kernel, with full xen support (live migration etc).

I tend to think that the default kernel should work with as much as
possible, but have some optimized kernel flavors for different needs.
For example linux-grsec for the real lowend without highmem, smp and
largblock deveices.

The drawback with many kernels is that it takes some extra time to
compile things. For example dahdi-linux driver and iscsi dirvers will be
need to be recompiled for each kernel flavor. This should ideally be
fully automated, but it is not right now.

Ideas, thoughts?

-nc



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---