From: Will Deacon <will.deacon@arm.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org, kvm-ppc@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH 0/7] kvmtool: Cleanup kernel loading
Date: Wed, 18 Nov 2015 17:08:04 +0000 [thread overview]
Message-ID: <20151118170804.GJ1588@arm.com> (raw)
In-Reply-To: <564C530A.3010604@arm.com>
On Wed, Nov 18, 2015 at 10:29:30AM +0000, Andre Przywara wrote:
> On 02/11/15 14:58, Will Deacon wrote:
> > On Fri, Oct 30, 2015 at 06:26:53PM +0000, Andre Przywara wrote:
> >> this series cleans up kvmtool's kernel loading functionality a bit.
> >> It has been broken out of a previous series I sent [1] and contains
> >> just the cleanup and bug fix parts, which should be less controversial
> >> and thus easier to merge ;-)
> >> I will resend the pipe loading part later on as a separate series.
> >>
> >> The first patch properly abstracts kernel loading to move
> >> responsibility into each architecture's code. It removes quite some
> >> ugly code from the generic kvm.c file.
> >> The later patches address the naive usage of read(2) to, well, read
> >> data from files. Doing this without coping with the subtleties of
> >> the UNIX read semantics (returning with less or none data read is not
> >> an error) can provoke hard to debug failures.
> >> So these patches make use of the existing and one new wrapper function
> >> to make sure we read everything we actually wanted to.
> >> The last patch moves the ARM kernel loading code into the proper
> >> location to be in line with the other architectures.
> >>
> >> Please have a look and give some comments!
> >
> > Looks good to me, but I'd like to see some comments from some mips/ppc/x86
> > people on the changes you're making over there.
>
> Sounds reasonable, but no answers yet.
>
> Can you take at least patch 1 and 2 meanwhile, preferably 6 and 7 (the
> ARM parts) also if you are OK with it?
> I have other patches that depend on 1/7 and 2/7, so having them upstream
> would help me and reduce further dependency churn.
> I am happy to resend the remaining patches for further discussion later.
We let them sit on the list for a while with no comments, so I just pushed
out your series. If a bug report shows up, then we can always revert the
offending patch if there's no quick fix.
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] kvmtool: Cleanup kernel loading
Date: Wed, 18 Nov 2015 17:08:04 +0000 [thread overview]
Message-ID: <20151118170804.GJ1588@arm.com> (raw)
In-Reply-To: <564C530A.3010604@arm.com>
On Wed, Nov 18, 2015 at 10:29:30AM +0000, Andre Przywara wrote:
> On 02/11/15 14:58, Will Deacon wrote:
> > On Fri, Oct 30, 2015 at 06:26:53PM +0000, Andre Przywara wrote:
> >> this series cleans up kvmtool's kernel loading functionality a bit.
> >> It has been broken out of a previous series I sent [1] and contains
> >> just the cleanup and bug fix parts, which should be less controversial
> >> and thus easier to merge ;-)
> >> I will resend the pipe loading part later on as a separate series.
> >>
> >> The first patch properly abstracts kernel loading to move
> >> responsibility into each architecture's code. It removes quite some
> >> ugly code from the generic kvm.c file.
> >> The later patches address the naive usage of read(2) to, well, read
> >> data from files. Doing this without coping with the subtleties of
> >> the UNIX read semantics (returning with less or none data read is not
> >> an error) can provoke hard to debug failures.
> >> So these patches make use of the existing and one new wrapper function
> >> to make sure we read everything we actually wanted to.
> >> The last patch moves the ARM kernel loading code into the proper
> >> location to be in line with the other architectures.
> >>
> >> Please have a look and give some comments!
> >
> > Looks good to me, but I'd like to see some comments from some mips/ppc/x86
> > people on the changes you're making over there.
>
> Sounds reasonable, but no answers yet.
>
> Can you take at least patch 1 and 2 meanwhile, preferably 6 and 7 (the
> ARM parts) also if you are OK with it?
> I have other patches that depend on 1/7 and 2/7, so having them upstream
> would help me and reduce further dependency churn.
> I am happy to resend the remaining patches for further discussion later.
We let them sit on the list for a while with no comments, so I just pushed
out your series. If a bug report shows up, then we can always revert the
offending patch if there's no quick fix.
Will
next prev parent reply other threads:[~2015-11-18 17:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 18:26 [PATCH 0/7] kvmtool: Cleanup kernel loading Andre Przywara
2015-10-30 18:26 ` Andre Przywara
2015-10-30 18:26 ` Andre Przywara
2015-10-30 18:26 ` [PATCH 1/7] Refactor kernel image loading Andre Przywara
2015-10-30 18:26 ` Andre Przywara
2015-10-30 18:26 ` [PATCH 2/7] provide generic read_file() implementation Andre Przywara
2015-10-30 18:26 ` Andre Przywara
2015-10-30 18:26 ` Andre Przywara
2015-10-30 18:26 ` [PATCH 3/7] powerpc: use read_file() in kernel and initrd loading Andre Przywara
2015-10-30 18:26 ` Andre Przywara
2015-10-30 18:26 ` Andre Przywara
2015-10-30 18:26 ` [PATCH 4/7] MIPS: use read wrappers in kernel loading Andre Przywara
2015-10-30 18:26 ` Andre Przywara
2015-10-30 18:26 ` Andre Przywara
2015-10-30 18:26 ` [PATCH 5/7] x86: " Andre Przywara
2015-10-30 18:26 ` Andre Przywara
2015-10-30 18:26 ` [PATCH 6/7] arm/arm64: use read_file() in kernel and initrd loading Andre Przywara
2015-10-30 18:26 ` Andre Przywara
2015-10-30 18:26 ` Andre Przywara
2015-10-30 18:27 ` [PATCH 7/7] arm: move kernel loading into arm/kvm.c Andre Przywara
2015-10-30 18:27 ` Andre Przywara
2015-10-30 18:27 ` Andre Przywara
2015-11-02 14:58 ` [PATCH 0/7] kvmtool: Cleanup kernel loading Will Deacon
2015-11-02 14:58 ` Will Deacon
2015-11-02 14:58 ` Will Deacon
2015-11-02 15:17 ` Dimitri John Ledkov
2015-11-02 15:17 ` Dimitri John Ledkov
2015-11-02 15:17 ` Dimitri John Ledkov
2015-11-02 16:03 ` Andre Przywara
2015-11-02 16:03 ` Andre Przywara
2015-11-02 16:03 ` Andre Przywara
2015-11-18 10:29 ` Andre Przywara
2015-11-18 10:29 ` Andre Przywara
2015-11-18 17:08 ` Will Deacon [this message]
2015-11-18 17:08 ` Will Deacon
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=20151118170804.GJ1588@arm.com \
--to=will.deacon@arm.com \
--cc=andre.przywara@arm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mpe@ellerman.id.au \
/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.