From: Pavel Fedin <p.fedin@samsung.com>
To: 'Christoffer Dall' <christoffer.dall@linaro.org>
Cc: 'Marc Zyngier' <marc.zyngier@arm.com>,
'Andre Przywara' <andre.przywara@arm.com>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Subject: RE: [PATCH v4 0/3] KVM: arm/arm64: Clean up some obsolete code
Date: Tue, 03 Nov 2015 12:44:54 +0300 [thread overview]
Message-ID: <002501d1161c$4c92f5d0$e5b8e170$@samsung.com> (raw)
In-Reply-To: <005201d11608$a73edf80$f5bc9e80$@samsung.com>
Hello!
> By this time i'll make a very minimal version of patch 0001, for you to test it. If we have
> problems with current 0001, which we
> cannot solve quickly, we could stick to that version then, which will provide the necessary
> changes to plug in LPIs, yet with
> minimal changes (it will only remove vgic_irq_lr_map).
> I guess i should have done it before. Or, i could even respin v5, with current 0001 split up.
> This should make it easier to bisect
> the problem.
So, i have just sent v5, conditions are the same as before. It is OK to stop at any point, and actually you should be able to
easily throw away 0003 and apply just 1, 2, 4. The minimum needed thing for LPIs introduction is 0001.
You can also stick to v4 if the problem does not get triggered by its first patch, if you prefer reduced commit log.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-11-03 9:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 8:37 [PATCH v4 0/3] KVM: arm/arm64: Clean up some obsolete code Pavel Fedin
2015-10-27 8:37 ` [PATCH v4 1/3] KVM: arm/arm64: Optimize away redundant LR tracking Pavel Fedin
2015-10-27 8:37 ` [PATCH v4 2/3] KVM: arm/arm64: Clean up vgic_retire_lr() and surroundings Pavel Fedin
2015-10-27 8:37 ` [PATCH v4 3/3] KVM: arm/arm64: Merge vgic_set_lr() and vgic_sync_lr_elrsr() Pavel Fedin
2015-11-02 21:15 ` [PATCH v4 0/3] KVM: arm/arm64: Clean up some obsolete code Christoffer Dall
2015-11-03 7:24 ` Pavel Fedin
2015-11-03 9:44 ` Pavel Fedin [this message]
2015-11-04 14:29 ` Christoffer Dall
2015-11-05 6:50 ` Pavel Fedin
2015-11-05 8:05 ` Peter Maydell
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='002501d1161c$4c92f5d0$e5b8e170$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
/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