qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: casmac <climber.cui@qq.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Implement standard file operation with QEMU
Date: Fri, 17 Jul 2020 23:18:00 +0800	[thread overview]
Message-ID: <tencent_DF5BA7114FBBA837DEBE64515ABC7CB27809@qq.com> (raw)

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

Hello Phil,
&nbsp;&nbsp; What I want to realize is to be able to call standard file operations (open, read, write etc) in the application program, and execute such programs in QEMU. But I am building under system mode.
&nbsp;&nbsp; TI provide copilation toolchain and a library that provide partial functionality from libc. I am hoping to use TI's toolkit to generate object code which contains calls to hook functions, and then use QEMU's host I/O implementation to realize low-level file operation. For example:

&nbsp; &nbsp; _stream[fildes]-&gt;WRITE&nbsp; <---hook to ---&gt;&nbsp;qemu_semihosting_console_outs
&nbsp; &nbsp;Are you suggesting that this is done by TCG helpers?


best regards,
xiaolei
&nbsp;&nbsp; 





------------------ Original ------------------
From:                                                                                                                        "Philippe Mathieu-Daudé"                                                                                    <f4bug@amsat.org&gt;;
Date:&nbsp;Thu, Jul 16, 2020 03:57 PM
To:&nbsp;"casmac"<climber.cui@qq.com&gt;;"qemu-devel"<qemu-devel@nongnu.org&gt;;"Alex Bennée"<alex.bennee@linaro.org&gt;;"Laurent Vivier"<lvivier@redhat.com&gt;;"Marc-André Lureau"<marcandre.lureau@redhat.com&gt;;

Subject:&nbsp;Re: Implement standard file operation with QEMU



Hi Xiaolei,

+Laurent (user-mode)
+Alex (semihosting)
+Marc-André (chardev)

On 7/16/20 2:51 AM, casmac wrote:
&gt; Hi all,
&gt; &nbsp; I am trying to implment standard file operation (stdio) with QEMU for
&gt; DSP architecture. The manufacture (TI) provides a runtime library that
&gt; support posix standard IO, but it left the device level implmentation as
&gt; hook function calls, like in the library source , it contains 
&gt; add_device() function, and write(),read(),open() are not implemented:
&gt; 
&gt; int add_device(char&nbsp; &nbsp; &nbsp; *name,
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; unsigned &nbsp; flags,
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; int&nbsp; &nbsp; &nbsp; (*dopen)&nbsp; (const char *path, unsigned flags, int
&gt; foo),
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; int&nbsp; &nbsp; &nbsp; (*dclose) (int fno),
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; int&nbsp; &nbsp; &nbsp; (*dread)&nbsp; (int fno, char *buf, unsigned count),
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; int&nbsp; &nbsp; &nbsp; (*dwrite) (int fno, const char *buf, unsigned
&gt; count),
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; fpos_t &nbsp; &nbsp; (*dlseek) (int fno, fpos_t offset, int origin),
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; int&nbsp; &nbsp; &nbsp; (*dunlink)(const char *path),
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; int&nbsp; &nbsp; &nbsp; (*drename)(const char *old_name, const char
&gt; *new_name))
&gt; {
&gt; &nbsp;&nbsp; _DEVICE *dt;
&gt; 
&gt; &nbsp;&nbsp; strncpy(dt-&gt;name,name,8);
&gt; &nbsp;&nbsp; dt-&gt;name[8] = '\0';
&gt; &nbsp;&nbsp; dt-&gt;flags &nbsp; = flags;
&gt; &nbsp;&nbsp; dt-&gt;OPEN&nbsp; &nbsp; = dopen;
&gt; &nbsp;&nbsp; dt-&gt;CLOSE &nbsp; = dclose;
&gt; &nbsp;&nbsp; dt-&gt;READ&nbsp; &nbsp; = dread;
&gt; &nbsp;&nbsp; dt-&gt;WRITE &nbsp; = dwrite;
&gt; &nbsp;&nbsp; dt-&gt;LSEEK &nbsp; = dlseek;
&gt; &nbsp;&nbsp; dt-&gt;UNLINK&nbsp; = dunlink;
&gt; &nbsp;&nbsp; dt-&gt;RENAME&nbsp; = drename;
&gt; }
&gt; 
&gt; int write(int&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; fildes,
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; const char &nbsp; *bufptr,
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; unsigned&nbsp; &nbsp; &nbsp; cnt)
&gt; {
&gt; &nbsp; 
&gt; /*------------------------------------------------------------------------*/
&gt; &nbsp;&nbsp; /* CALL FUNCTION FROM DEVICE TABLE TO PERFORM WRITE FOR THIS
&gt; DEVICE/FILE&nbsp; */
&gt; &nbsp; 
&gt; /*------------------------------------------------------------------------*/
&gt; &nbsp;&nbsp; return (*(_stream[fildes]-&gt;WRITE)) (fildes,bufptr,cnt);
&gt; }
&gt; 
&gt; &nbsp;&nbsp; Then, how can we use this runtime library together with QEMu to
&gt; implement full-stack file oerations?&nbsp; I really appreaciate any advice.

Trying to understand...

Are you trying to ask "how to implement semihosting for my
qemu-user-tidsp fork"?

Have a look at "hw/semihosting/console.h" and the implementation
(so far only ARM) of qemu_semihosting_console_[in/out].
This might help to plug read/write. Using other stream than
stdin/stdout is not supported (but you can add support) so
open/lseek/close/rename/unlink are not considered.

(for QEMU 'console' is the stdin/stdout subset of stdio).

You can redirect semihosted files with any host chardev,
this is done in qemu_semihosting_connect_chardevs().

You might also have a look at the functions declared in
"hw/semihosting/semihost.h" and how the different TCG helpers
use them.

Regards,

Phil.

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

             reply	other threads:[~2020-07-17 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 15:18 casmac [this message]
2020-07-17 15:43 ` Implement standard file operation with QEMU Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2020-07-16  0:51 casmac
2020-07-16  7:57 ` Philippe Mathieu-Daudé

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=tencent_DF5BA7114FBBA837DEBE64515ABC7CB27809@qq.com \
    --to=climber.cui@qq.com \
    --cc=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=lvivier@redhat.com \
    --cc=marcandre.lureau@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).