From: Julien Grall <julien@xen.org>
To: Jan Beulich <jbeulich@suse.com>,
Julien Grall <julien.grall.oss@gmail.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <Ian.Jackson@citrix.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
George Dunlap <George.Dunlap@citrix.com>
Subject: Re: [PATCH v2 for-4.15 3/7] CHANGELOG.md: Add dom0/domU zstd compression support
Date: Tue, 30 Mar 2021 16:34:57 +0100 [thread overview]
Message-ID: <92f0b44a-84de-457c-ba04-896644382905@xen.org> (raw)
In-Reply-To: <672c88ac-8373-6629-4d2f-0d1e86c103cd@suse.com>
On 30/03/2021 11:56, Jan Beulich wrote:
> On 30.03.2021 12:14, Julien Grall wrote:
>>
>>
>> On 30/03/2021 11:08, George Dunlap wrote:
>>>
>>>
>>>> On Mar 29, 2021, at 7:54 PM, Julien Grall <julien.grall.oss@gmail.com> wrote:
>>>>
>>>> Hi George,
>>>>
>>>> On Mon, 29 Mar 2021 at 17:15, George Dunlap <george.dunlap@citrix.com> wrote:
>>>>> diff --git a/CHANGELOG.md b/CHANGELOG.md
>>>>> index 8c89212f14..538eae611c 100644
>>>>> --- a/CHANGELOG.md
>>>>> +++ b/CHANGELOG.md
>>>>> @@ -12,6 +12,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
>>>>> - ARM SMMUv3 (Tech Preview)
>>>>> - Intel Processor Trace support (Tech Preview)
>>>>> - Named PCI devices for xl/libxl
>>>>> + - Support for zstd-compressed dom0 and domU kernels
>>>>
>>>> Looking at the log, the feature looks x86 only (at least the dom0 part).
>>>
>>> Oh, interesting. So what about the following?
>>>
>>> - Support for zstd-compressed dom0 (x86) and domU kernels
>>
>> Sounds fine to me. Note that I haven't tried zstd-compressed for domu
>> Kernel on Arm.
>>
>> Maybe the author (Jan) can confirm whether this was plumbed in common
>> libxc code?
>
> Well, I've followed the model used for other compression methods. I have
> no idea what this means or does not mean for Arm; in fact so far I was
> under the impression that like in the hypervisor decompression support
> was an x86-only feature, but from what you say I conclude I have been
> wrong with this.
We support gzip for dom0. For guests, I am not entirely sure what the
state as I tend to uncompressed kernel every time.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2021-03-30 15:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 16:14 [PATCH v2 for-4.15 1/7] Intel Processor Trace Support: Add CHANGELOG.md and SUPPORT.md entries George Dunlap
2021-03-29 16:14 ` [PATCH v2 for-4.15 2/7] CHANGELOG.md: Add named PCI devices George Dunlap
2021-03-29 16:14 ` [PATCH v2 for-4.15 3/7] CHANGELOG.md: Add dom0/domU zstd compression support George Dunlap
2021-03-29 17:01 ` Ian Jackson
2021-03-29 17:05 ` Ian Jackson
2021-03-29 18:54 ` Julien Grall
2021-03-30 10:08 ` George Dunlap
2021-03-30 10:14 ` Julien Grall
2021-03-30 10:56 ` Jan Beulich
2021-03-30 15:34 ` Julien Grall [this message]
2021-03-30 10:56 ` Jan Beulich
2021-03-29 16:14 ` [PATCH v2 for-4.15 4/7] CHANGELOG.md: NetBSD lib/gnttab support George Dunlap
2021-03-29 16:14 ` [PATCH v2 for-4.15 5/7] CHANGELOG.md: Add entries for emulation George Dunlap
2021-03-29 16:14 ` [PATCH v2 for-4.15 6/7] CHANGELOG.md: Add entries for CI loop George Dunlap
2021-03-29 23:38 ` Stefano Stabellini
2021-03-29 16:14 ` [PATCH v2 for-4.15 7/7] CHANGELOG.md: Make PV shim smaller by factoring out HVM-specific shadow code George Dunlap
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=92f0b44a-84de-457c-ba04-896644382905@xen.org \
--to=julien@xen.org \
--cc=Andrew.Cooper3@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall.oss@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).