All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-devel@nongnu.org, lvivier@redhat.com
Subject: Re: [Qemu-devel] [PATCH 02/10] cuda: don't allow writes to port output pins
Date: Mon, 5 Feb 2018 16:53:25 -0300	[thread overview]
Message-ID: <ede27bd5-033e-ef2d-d8e6-bf6956a2bd80@amsat.org> (raw)
In-Reply-To: <20180203103727.26457-3-mark.cave-ayland@ilande.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

On 02/03/2018 07:37 AM, Mark Cave-Ayland wrote:
> Use the direction registers as a mask to ensure that only input pins are
> updated upon write.
> 
> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
> ---
>  hw/misc/macio/cuda.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/misc/macio/cuda.c b/hw/misc/macio/cuda.c
> index 23b7e0f5b0..7214e7adcb 100644
> --- a/hw/misc/macio/cuda.c
> +++ b/hw/misc/macio/cuda.c
> @@ -359,11 +359,11 @@ static void cuda_write(void *opaque, hwaddr addr, uint64_t val, unsigned size)
>  
>      switch(addr) {
>      case CUDA_REG_B:
> -        s->b = val;
> +        s->b = (s->b & ~s->dirb) | (val & s->dirb);

I personally find it easier to read in 2 lines (&=~, |=)

It might be useful to log invalid guest values:

           if (val & ~s->dirb) {
               GUEST_ERROR();
               val &= s->dirb;
           }
           s->b |= val;

>          cuda_update(s);
>          break;
>      case CUDA_REG_A:
> -        s->a = val;
> +        s->a = (s->a & ~s->dira) | (val & s->dira);

Ditto.

Regardless:
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>

>          break;
>      case CUDA_REG_DIRB:
>          s->dirb = val;
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-02-05 19:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-03 10:37 [Qemu-devel] [PATCH 00/10] cuda: various fixes, and move 6522 to separate device Mark Cave-Ayland
2018-02-03 10:37 ` [Qemu-devel] [PATCH 01/10] cuda: do not use old_mmio accesses Mark Cave-Ayland
2018-02-05 14:17   ` Laurent Vivier
2018-02-06 21:40     ` Mark Cave-Ayland
2018-02-03 10:37 ` [Qemu-devel] [PATCH 02/10] cuda: don't allow writes to port output pins Mark Cave-Ayland
2018-02-05 14:27   ` Laurent Vivier
2018-02-05 19:53   ` Philippe Mathieu-Daudé [this message]
2018-02-03 10:37 ` [Qemu-devel] [PATCH 03/10] cuda: don't call cuda_update() when writing to ACR register Mark Cave-Ayland
2018-02-03 10:37 ` [Qemu-devel] [PATCH 04/10] cuda: introduce CUDAState parameter to get_counter() Mark Cave-Ayland
2018-02-05 19:44   ` Philippe Mathieu-Daudé
2018-02-03 10:37 ` [Qemu-devel] [PATCH 05/10] cuda: rename frequency property to tb_frequency Mark Cave-Ayland
2018-02-05 19:45   ` Philippe Mathieu-Daudé
2018-02-03 10:37 ` [Qemu-devel] [PATCH 06/10] cuda: minor cosmetic tidy-ups to get_next_irq_time() Mark Cave-Ayland
2018-02-05 19:39   ` Philippe Mathieu-Daudé
2018-02-03 10:37 ` [Qemu-devel] [PATCH 07/10] cuda: set timer 1 frequency property to CUDA_TIMER_FREQ Mark Cave-Ayland
2018-02-03 10:37 ` [Qemu-devel] [PATCH 08/10] cuda: factor out timebase-derived counter value and load time Mark Cave-Ayland
2018-02-05 19:44   ` Philippe Mathieu-Daudé
2018-02-06 21:44     ` Mark Cave-Ayland
2018-02-03 10:37 ` [Qemu-devel] [PATCH 09/10] misc: introduce new mos6522 VIA device and enable it for ppc builds Mark Cave-Ayland
2018-02-03 10:37 ` [Qemu-devel] [PATCH 10/10] cuda: convert to use the shared mos6522 device Mark Cave-Ayland
2018-02-03 11:11 ` [Qemu-devel] [PATCH 00/10] cuda: various fixes, and move 6522 to separate device no-reply
2018-02-03 11:14   ` Mark Cave-Ayland

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=ede27bd5-033e-ef2d-d8e6-bf6956a2bd80@amsat.org \
    --to=f4bug@amsat.org \
    --cc=lvivier@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.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 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.