qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: boddu pavan <boddupavan@yahoo.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU data passing between modules
Date: Tue, 10 Feb 2015 13:34:00 +0000 (UTC)	[thread overview]
Message-ID: <1082716497.1535621.1423575240072.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <54DA07DD.4000206@redhat.com>

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

Yes its hardware block, and yes they are of same SOC. status is 16bit. 

     On Tuesday, February 10, 2015 7:00 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
   

 [no private messages please]

On 10/02/2015 14:27, boddu pavan wrote:
> Hi paolo,
> I have a aes module and its status should also be updated in register of
> another block, which is said to be public register. The one in which its
> updating is a private register. 
> How to get the data passed and updated in another module. I see using a
> dma for register update is heavy, is there any simple one.
> 

How do you define a "module"?  Is it a hardware block that you're
emulating (a DeviceState)?  Are the two modules part of the same SoC?
How large is the status?

Paolo



   

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

  reply	other threads:[~2015-02-10 13:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54DA05BA.4030106@redhat.com>
     [not found] ` <832065415.1546511.1423574820829.JavaMail.yahoo@mail.yahoo.com>
2015-02-10 13:30   ` [Qemu-devel] QEMU data passing between modules Paolo Bonzini
2015-02-10 13:34     ` boddu pavan [this message]
2015-02-10 13:39       ` Paolo Bonzini
2015-02-10 14:02         ` boddu pavan
2015-02-10 14:25           ` Paolo Bonzini
2015-02-10 18:20             ` boddu pavan
2015-02-11  8:42               ` boddu pavan
2015-02-10 13:15 boddu pavan

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=1082716497.1535621.1423575240072.JavaMail.yahoo@mail.yahoo.com \
    --to=boddupavan@yahoo.com \
    --cc=pbonzini@redhat.com \
    --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 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).