at all. The experiment shows:
kernel kernel sizetime in decompress_kernel
compressed (gzip)3.3M 53ms
compressed (lz4) 4.5M 16ms
uncompressed 14M2ms
Signed-off-by: Chao Peng <chao.p.p...@linux.intel.com>
at all. The experiment shows:
kernel kernel sizetime in decompress_kernel
compressed (gzip)3.3M 53ms
compressed (lz4) 4.5M 16ms
uncompressed 14M2ms
Signed-off-by: Chao Peng
---
v2:
* add HAVE_KERNEL_RAW
On Mon, 2017-03-27 at 15:25 +0200, Arnd Bergmann wrote:
> On Mon, Mar 27, 2017 at 1:47 PM, Michal Marek <mma...@suse.com> wrote:
> >
> > Dne 27.3.2017 v 09:58 Sebastian Andrzej Siewior napsal(a):
> > >
> > > On 2017-
On Mon, 2017-03-27 at 15:25 +0200, Arnd Bergmann wrote:
> On Mon, Mar 27, 2017 at 1:47 PM, Michal Marek wrote:
> >
> > Dne 27.3.2017 v 09:58 Sebastian Andrzej Siewior napsal(a):
> > >
> > > On 2017-03-24
On Mon, 2017-03-27 at 09:58 +0200, Sebastian Andrzej Siewior wrote:
> On 2017-03-24 13:35:40 [+0800], Chao Peng wrote:
> >
> >
> > >
> > > >
> > > > >
> > > > > kernel kernel sizetime in
> > > &
On Mon, 2017-03-27 at 09:58 +0200, Sebastian Andrzej Siewior wrote:
> On 2017-03-24 13:35:40 [+0800], Chao Peng wrote:
> >
> >
> > >
> > > >
> > > > >
> > > > > kernel kernel sizetime in
> > > &
> > > The patch adds a 'CONFIG_KERNEL_RAW' configure choice so the built
> > > binary
> > > can have no uncompressing at all. The experiment shows:
> > >
> > > kernel kernel sizetime in decompress_kernel
> > > compressed (gzip)3.3M 53ms
> > >
> > > The patch adds a 'CONFIG_KERNEL_RAW' configure choice so the built
> > > binary
> > > can have no uncompressing at all. The experiment shows:
> > >
> > > kernel kernel sizetime in decompress_kernel
> > > compressed (gzip)3.3M 53ms
> > >
14M3ms
Signed-off-by: Chao Peng <chao.p.p...@linux.intel.com>
---
arch/x86/boot/compressed/Makefile | 3 +++
arch/x86/boot/compressed/misc.c | 14 ++
init/Kconfig | 7 +++
scripts/Makefile.lib | 8
4 files c
14M3ms
Signed-off-by: Chao Peng
---
arch/x86/boot/compressed/Makefile | 3 +++
arch/x86/boot/compressed/misc.c | 14 ++
init/Kconfig | 7 +++
scripts/Makefile.lib | 8
4 files changed, 32 insertions(+)
diff --git
Guest segment selector is 16 bit field and guest segment base is natural
width field. Fix two incorrect invocations accordingly.
Without this patch, build fails when aggressive inlining is used with ICC.
Cc: sta...@vger.kernel.org
Signed-off-by: Chao Peng <chao.p.p...@linux.intel.com>
---
Guest segment selector is 16 bit field and guest segment base is natural
width field. Fix two incorrect invocations accordingly.
Without this patch, build fails when aggressive inlining is used with ICC.
Cc: sta...@vger.kernel.org
Signed-off-by: Chao Peng
---
arch/x86/kvm/vmx.c | 4 ++--
1
On Wed, 2017-02-15 at 17:42 +0100, Paolo Bonzini wrote:
>
> On 15/02/2017 15:41, Chao Peng wrote:
> >
> > Multiboot specification
> > (http://git.savannah.gnu.org/cgit/grub.git/tree/doc/multiboot.texi?h=mul
> > tiboot2)
> > is an open standard that
On Wed, 2017-02-15 at 17:42 +0100, Paolo Bonzini wrote:
>
> On 15/02/2017 15:41, Chao Peng wrote:
> >
> > Multiboot specification
> > (http://git.savannah.gnu.org/cgit/grub.git/tree/doc/multiboot.texi?h=mul
> > tiboot2)
> > is an open standard that
> > Just something to consider, provided the issues with multiboot get
> > resolved:
> >
> > If you want to boot Xen you actually use the multiboot protocol, the
> > last PVH
> > boot patches had borrowed ideas from Multiboot to add an entry to
> > Linux, only
> > it was Xen'ified. What would be
> > Just something to consider, provided the issues with multiboot get
> > resolved:
> >
> > If you want to boot Xen you actually use the multiboot protocol, the
> > last PVH
> > boot patches had borrowed ideas from Multiboot to add an entry to
> > Linux, only
> > it was Xen'ified. What would be
, the entry
address (0x100) is actually phiscial address, grub refuses to load it
by saying: 'entry point isn't in a segment'.
This patch is sent out as RFC in case you have some ideas.
Signed-off-by: Chao Peng <chao.p.p...@linux.intel.com>
---
arch/x86/Kconfig | 6 +
ar
, the entry
address (0x100) is actually phiscial address, grub refuses to load it
by saying: 'entry point isn't in a segment'.
This patch is sent out as RFC in case you have some ideas.
Signed-off-by: Chao Peng
---
arch/x86/Kconfig | 6 +
arch/x86/Makefile| 4
sn't have this restriction anymore (all the tasks can be moved out
of the default group), hence:
Reviewed-by: Chao Peng
Chao
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.k
sn't have this restriction anymore (all the tasks can be moved out
of the default group), hence:
Reviewed-by: Chao Peng <chao.p.p...@linux.intel.com>
Chao
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kerne
On Wed, Nov 18, 2015 at 10:01:54PM -0200, Marcelo Tosatti wrote:
> > tglx
>
> Again: you don't need to look into the MSR table and relate it
> to tasks if you store the data as:
>
> task group 1 = {
> reservation-1 = {size = 80Kb, type = data, socketmask =
>
On Wed, Nov 18, 2015 at 10:01:54PM -0200, Marcelo Tosatti wrote:
> > tglx
>
> Again: you don't need to look into the MSR table and relate it
> to tasks if you store the data as:
>
> task group 1 = {
> reservation-1 = {size = 80Kb, type = data, socketmask =
>
On Wed, Nov 18, 2015 at 07:25:03PM +0100, Thomas Gleixner wrote:
>
> Let's look at partitioning itself. We have two options:
>
>1) Per task partitioning
>
>2) Per CPU partitioning
>
> So far we only talked about #1, but I think that #2 has a value as
> well. Let me give you a simple
On Wed, Nov 18, 2015 at 07:25:03PM +0100, Thomas Gleixner wrote:
>
> Let's look at partitioning itself. We have two options:
>
>1) Per task partitioning
>
>2) Per CPU partitioning
>
> So far we only talked about #1, but I think that #2 has a value as
> well. Let me give you a simple
On Wed, Oct 22, 2014 at 12:17:33PM +0200, Paolo Bonzini wrote:
> On 10/22/2014 11:35 AM, Chao Peng wrote:
> > Expose Intel AVX-512 feature bits to guest. Also add checks for
> > xcr0 AVX512 related bits according to spec:
> > http://download-software.intel.com/sites/defaul
Expose Intel AVX-512 feature bits to guest. Also add checks for
xcr0 AVX512 related bits according to spec:
http://download-software.intel.com/sites/default/files/managed/71/2e/319433-017.pdf
Signed-off-by: Chao Peng
---
arch/x86/include/asm/xsave.h |1 +
arch/x86/kvm/cpuid.c |3
On Wed, Oct 22, 2014 at 12:17:33PM +0200, Paolo Bonzini wrote:
On 10/22/2014 11:35 AM, Chao Peng wrote:
Expose Intel AVX-512 feature bits to guest. Also add checks for
xcr0 AVX512 related bits according to spec:
http://download-software.intel.com/sites/default/files/managed/71/2e/319433-017
Expose Intel AVX-512 feature bits to guest. Also add checks for
xcr0 AVX512 related bits according to spec:
http://download-software.intel.com/sites/default/files/managed/71/2e/319433-017.pdf
Signed-off-by: Chao Peng chao.p.p...@linux.intel.com
---
arch/x86/include/asm/xsave.h |1 +
arch/x86
28 matches
Mail list logo
