From: Steve Rutherford <srutherford@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH kvm-unit-tests] x86: ioapic: add tests around retriggering of level interrupts
Date: Wed, 29 Jul 2015 20:14:48 -0700 [thread overview]
Message-ID: <20150730031448.GB15229@google.com> (raw)
In-Reply-To: <1438176493-26033-1-git-send-email-pbonzini@redhat.com>
On Wed, Jul 29, 2015 at 03:28:13PM +0200, Paolo Bonzini wrote:
> Test resampling of level interrupts after EOI, by leaving the IRQ
> line set in the ISR. One tests does reset the IRQ line after a while,
> the other uses masking instead in the ISR.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> x86/ioapic.c | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 51 insertions(+)
>
> diff --git a/x86/ioapic.c b/x86/ioapic.c
> index 1fcf67e..d43d5c1 100644
> --- a/x86/ioapic.c
> +++ b/x86/ioapic.c
> @@ -188,6 +188,31 @@ static void test_ioapic_level_sequential(void)
> report("sequential level interrupts", g_isr_99 == 2);
> }
>
> +static volatile int g_isr_9a;
> +
> +static void ioapic_isr_9a(isr_regs_t *regs)
> +{
> + ++g_isr_9a;
> + if (g_isr_9a == 2)
> + set_irq_line(0x0e, 0);
> + eoi();
> +}
> +
> +static void test_ioapic_level_retrigger(void)
> +{
> + handle_irq(0x9a, ioapic_isr_9a);
> + set_ioapic_redir(0x0e, 0x9a, LEVEL_TRIGGERED);
> +
> + asm volatile ("cli");
> + set_irq_line(0x0e, 1);
> + while (g_isr_9a != 2)
> + asm volatile ("sti; hlt; cli");
This seems sketchy. The test should be able to exit this and fail.
Steve
next prev parent reply other threads:[~2015-07-30 3:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 13:28 [PATCH kvm-unit-tests] x86: ioapic: add tests around retriggering of level interrupts Paolo Bonzini
2015-07-30 3:14 ` Steve Rutherford [this message]
2015-07-30 7:13 ` Paolo Bonzini
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=20150730031448.GB15229@google.com \
--to=srutherford@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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.