All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Ross Burton <ross@burtonini.com>, Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] qemu: always define unknown_lock_type
Date: Wed, 16 Sep 2020 16:02:45 +0800	[thread overview]
Message-ID: <378f4a7f-b201-daed-6f2d-8bec94fc82dd@windriver.com> (raw)
In-Reply-To: <CAAnfSTvE_wrt6DUGxPGQefJ4uF_0CZaPvpAtUsBJzoVUqbfjRA@mail.gmail.com>



On 9/15/20 6:26 PM, Ross Burton wrote:
> On Mon, 14 Sep 2020 at 16:23, Khem Raj <raj.khem@gmail.com> wrote:
> 
>>>> perhaps you are not using one of -O<n> option ?
>>>
>>> -Og passed to the compiler as DEBUG_BUILD = "1" defined in local.conf.
>>
>> Does qemu work when built with -Og
> 
> This is the pertinent question.  If qemu doesn't run after
> un-upstreamable patches when built with -Og, what's the point?
> Debuggable code that you can't execute serves no purpose.
> 
> If qemu *needs* to be optimised to actually execute then override
> DEBUG_BUILD to optimise at the lowest usable level.

Thanks! Will sent a patch to override DEBUG_BUILD for qemu.

> 
> Ross
> 
> 
> 
> 

      reply	other threads:[~2020-09-16  8:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10  2:57 [PATCH] qemu: always define unknown_lock_type Yu, Mingli
2020-09-10 10:41 ` [OE-core] " Ross Burton
2020-09-14  1:50   ` Yu, Mingli
2020-09-14  5:26     ` Khem Raj
2020-09-14  5:44       ` Yu, Mingli
2020-09-14  6:02         ` Khem Raj
2020-09-14  6:25           ` Yu, Mingli
2020-09-14 15:23             ` Khem Raj
2020-09-14 16:50               ` Joe Slater
2020-09-15 10:26               ` Ross Burton
2020-09-16  8:02                 ` Yu, Mingli [this message]

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=378f4a7f-b201-daed-6f2d-8bec94fc82dd@windriver.com \
    --to=mingli.yu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=ross@burtonini.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 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.