All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Nitesh Narayan Lal <nitesh@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	thuth@redhat.com, nilal@redhat.com, kvm@vger.kernel.org,
	pbonzini@redhat.com
Subject: Re: [Patch v1] x86: Fix the logical destination mode test
Date: Tue, 14 Apr 2020 18:11:40 +0200	[thread overview]
Message-ID: <87r1wqxd1f.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <3c9c379c-c027-2793-6148-3b677054740e@redhat.com>

Nitesh Narayan Lal <nitesh@redhat.com> writes:

> On 4/14/20 11:30 AM, Vitaly Kuznetsov wrote:
>> Nitesh Narayan Lal <nitesh@redhat.com> writes:
>>
>>> On 4/14/20 10:01 AM, Vitaly Kuznetsov wrote:
>>>> Also, this patch could've been split.
>>> I can divide it 2 parts:
>>> 1. support for logical destination mode.
>>> 2. support for physical destination mode. I can also fix  the above issue in
>>> this patch itself.
>>> Does that make sense?
>> Too late, it's already commited :-) I just meant to say that
>> e.g. spinlock part could've been split into its own patch, unittests.cfg
>> - another one,...
>
> Ah, I see. I will be more careful.
> For now,  I will just move the physical destination mode test back under
> the check. Will that be acceptable as a standalone patch?

This is already in Paolo's patch:
https://lore.kernel.org/kvm/87zhbexh3v.fsf@vitty.brq.redhat.com/T/#m9791cd50a9d82fabdaddcb9259d14df3b89ed250

> In between I have a question is it normal for test_ioapic_self_reconfigure()
> to fail when executed with irqchip split?
> If so do we expect that it will leave the VM in some sort of dirty state
> that causes the following test to fail?

Not sure I got your question but IMO when someone does
./run_tests.sh
all tests are supposed to pass -- unless there is a bug in KVM (e.g. the
person is running an old kernel). In case we're seeing failures (or,
even worse, hangs) with the latest upstream kernel -- something is
broken, either KVM or kvm-unit-tests.

-- 
Vitaly


  reply	other threads:[~2020-04-14 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1583795750-33197-1-git-send-email-nitesh@redhat.com>
2020-03-09 23:25 ` [Patch v1] x86: Fix the logical destination mode test Nitesh Narayan Lal
2020-03-10 14:03 ` Marcelo Tosatti
2020-03-16 22:27   ` Nitesh Narayan Lal
2020-03-17 15:43     ` Paolo Bonzini
2020-04-14 14:01     ` Vitaly Kuznetsov
2020-04-14 15:14       ` Nitesh Narayan Lal
2020-04-14 15:30         ` Vitaly Kuznetsov
2020-04-14 15:34           ` Nitesh Narayan Lal
2020-04-14 16:11             ` Vitaly Kuznetsov [this message]
2020-04-14 16:27               ` Nitesh Narayan Lal

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=87r1wqxd1f.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=nilal@redhat.com \
    --cc=nitesh@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=thuth@redhat.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 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.