All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adnan Khaleel" <adnan@khaleel.us>
To: Richard Henderson <rth@twiddle.net>
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Single 64bit memory transaction instead of two 32bit memory transaction
Date: Sat, 03 Sep 2011 17:36:42 -0500	[thread overview]
Message-ID: <20110903223642.356831a4@shadowfax.no-ip.com> (raw)
In-Reply-To: 4E61889A.9080707@twiddle.net

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

Is there a patch for the new MemoryRegion API? 


At least for now, I need to be able to issue a single 64, 128 or 256bit transaction to a particular IO device. Is there a way I can do this now as a temp solution? I don't mind coalescing the bytes as they are issued by Qemu but I have no way to know that they're from the same instruction. Any pointers?


Thanks,


AK
  _____  

From: Richard Henderson [mailto:rth@twiddle.net]
To: adnan@khaleel.us
Cc: qemu-devel@nongnu.org, blauwirbel@gmail.com
Sent: Fri, 02 Sep 2011 20:53:30 -0500
Subject: Re: [Qemu-devel] Single 64bit memory transaction instead of two 32bit memory transaction

On 09/02/2011 12:46 AM, Adnan Khaleel wrote:
  > Is there anyway we can prevent Qemu breaking up 64,128 and 256bit XMM or YMM instructions into smaller chunks and have them issue as a single transaction of the original width?
  
  Not yet.  The new MemoryRegion API will allow this, but we need to convert all 
  the devices first, then rip out the old API.
  
  It's a work in progress...
  
  
  r~
    

[-- Attachment #2: Type: text/html, Size: 1592 bytes --]

             reply	other threads:[~2011-09-03 22:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-03 22:36 Adnan Khaleel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-09-01 19:16 [Qemu-devel] Single 64bit memory transaction instead of two 32bit memory transaction Adnan Khaleel
2011-09-03  1:53 ` Richard Henderson
2010-11-08 23:27 Adnan Khaleel
2010-11-09 17:57 ` Blue Swirl

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=20110903223642.356831a4@shadowfax.no-ip.com \
    --to=adnan@khaleel.us \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.