qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: John Snow <jsnow@redhat.com>, Reza Jelveh <reza.jelveh@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ahci.c: mask the interrupt on complete flag to allow ahci.c to read the correct size for the PRDT
Date: Fri, 27 Jun 2014 18:19:49 +0200	[thread overview]
Message-ID: <53AD99A5.7000707@suse.de> (raw)
In-Reply-To: <53AD8C6A.3040709@redhat.com>


On 27.06.14 17:23, John Snow wrote:
>
> On 06/26/2014 07:28 PM, Reza Jelveh wrote:
>> +#define AHCI_PRDT_SIZE_MASK                0x3fffff
>>
> out of rampant curiosity, is there ever a case where the lower bits 
> might be set and the mask 0x3fffc is not desirable, or can we always 
> trust those bits to simply be off anyway?

We can't really trust anything from an OS :). But the reason for this 
patch is that PRDT.I was set on some entries to enable notification of 
the OS when the entry has been successfully processed.

We currently don't emulate the I bit correctly, but get away without 
doing so. However, we have to make sure we mask it out when interpreting 
the values. Hence the mask.

I do agree that this should have been in the patch description. Reza, 
could you please repost this with a proper patch description and as a 
checkpatch.pl compliant patch? Also please CC me on the next iteration :).


Alex

PS: Is your name really John Snow? That is so cool!

  reply	other threads:[~2014-06-27 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 23:28 [Qemu-devel] [PATCH] ahci.c: mask the interrupt on complete flag to allow ahci.c to read the correct size for the PRDT Reza Jelveh
2014-06-27 11:35 ` Paolo Bonzini
2014-06-27 15:23 ` John Snow
2014-06-27 16:19   ` Alexander Graf [this message]
2014-06-27 16:33     ` Reza Jelveh
2014-06-27 16:38       ` Alexander Graf

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=53AD99A5.7000707@suse.de \
    --to=agraf@suse.de \
    --cc=jsnow@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=reza.jelveh@gmail.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;
as well as URLs for NNTP newsgroup(s).