qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* How to comminicate between two QOM model?
@ 2021-09-02  6:40 Duo jia
  2021-09-02  7:07 ` Klaus Jensen
  0 siblings, 1 reply; 2+ messages in thread
From: Duo jia @ 2021-09-02  6:40 UTC (permalink / raw)
  To: QEMU Developers

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

HI,
I has two QOM model,A and B, When A‘s register changed,B’s register will
should also be change .

I dont konw  how to change B's reg in A device .

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: How to comminicate between two QOM model?
  2021-09-02  6:40 How to comminicate between two QOM model? Duo jia
@ 2021-09-02  7:07 ` Klaus Jensen
  0 siblings, 0 replies; 2+ messages in thread
From: Klaus Jensen @ 2021-09-02  7:07 UTC (permalink / raw)
  To: Duo jia; +Cc: QEMU Developers

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

On Sep  2 14:40, Duo jia wrote:
> HI,
> I has two QOM model,A and B, When A‘s register changed,B’s register will
> should also be change .
> 
> I dont konw  how to change B's reg in A device .

There are a couple of ways you can "plumb" devices and objects together.
For devices you can use a qdev bus if you have a strict parent/child
relationship between A and B. Or you can use a "link" property to
manually wire up the devices/objects. Or use can use object composition
(device A creates a child object B).

But I think it depends a lot on what you are actually modeling and you
are not sharing a lot of information on that ;)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-09-02  7:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-09-02  6:40 How to comminicate between two QOM model? Duo jia
2021-09-02  7:07 ` Klaus Jensen

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).