Displaying 12 results from an estimated 12 matches for "debugon".
Did you mean:
debug_on
2009 May 03
1
[LLVMdev] Calling-convention lowering proposal
...changed.
>
> You can turn it on once, but you can never turn it off again.
That's not different from before.
> That is, unless there is some way to do it other than by passing
> command line options to cl::ParseCommandLineOptions. The last
> time I looked the problem was that DebugOnly was defined as
> cl::ValueRequired rather than cl::OneOrMore, so the CLI would
> reject any subsequent setting.
>
> If there is some way around this, I'd be delighted to know.
This will require modifying code. Patches welcome.
Evan
>
> Andrew.
>
> __________________...
2009 May 01
0
[LLVMdev] Calling-convention lowering proposal
...gt;
> That's not true. It's just the option name was changed.
You can turn it on once, but you can never turn it off again.
That is, unless there is some way to do it other than by passing
command line options to cl::ParseCommandLineOptions. The last
time I looked the problem was that DebugOnly was defined as
cl::ValueRequired rather than cl::OneOrMore, so the CLI would
reject any subsequent setting.
If there is some way around this, I'd be delighted to know.
Andrew.
2009 May 01
2
[LLVMdev] Calling-convention lowering proposal
On Apr 30, 2009, at 11:27 AM, Andrew Haley wrote:
> Chris Lattner wrote:
>> On Apr 30, 2009, at 9:38 AM, David Greene wrote:
>>> On Wednesday 29 April 2009 19:22, Chris Lattner wrote:
>>>> On Apr 29, 2009, at 8:39 AM, David Greene wrote:
>>>>> This patch changes the LLVM API. We should have a process for
>>>>> deprecating
2009 Jan 21
0
[LLVMdev] Load from abs address generated bad code on LLVM 2.4
On Jan 21, 2009, at 4:15 AM, Andrew Haley wrote:
>> That should work fine, just use "jit" instead of "x86-emitter" as the
>> debug type.
>
> That's impossible: CurrentDebugType is now private; it appears
> nowhere in the installed headers. I can't find any public interface
> to allow a JIT to set it.
Ah ok. I'd suggest doing what llvm-gcc
2019 Jul 18
4
[PATCH] virtio-net: parameterize min ring num_free for virtio receive
On Thu, Jul 18, 2019 at 10:42:47AM -0400, Michael S. Tsirkin wrote:
> On Thu, Jul 18, 2019 at 10:01:05PM +0800, Jason Wang wrote:
> >
> > On 2019/7/18 ??9:04, Michael S. Tsirkin wrote:
> > > On Thu, Jul 18, 2019 at 12:55:50PM +0000, ? jiang wrote:
> > > > This change makes ring buffer reclaim threshold num_free configurable
> > > > for better
2019 Jul 18
4
[PATCH] virtio-net: parameterize min ring num_free for virtio receive
On Thu, Jul 18, 2019 at 10:42:47AM -0400, Michael S. Tsirkin wrote:
> On Thu, Jul 18, 2019 at 10:01:05PM +0800, Jason Wang wrote:
> >
> > On 2019/7/18 ??9:04, Michael S. Tsirkin wrote:
> > > On Thu, Jul 18, 2019 at 12:55:50PM +0000, ? jiang wrote:
> > > > This change makes ring buffer reclaim threshold num_free configurable
> > > > for better
2019 Jul 23
2
[PATCH] virtio-net: parameterize min ring num_free for virtio receive
...gt; (@cast($vq, "vring_virtqueue")->vring->used->idx) ---> we use this one
>>> to verify if we run out of free buffer in avail ring
>>> ??? if (y<0 && (y+65535)<4096)
>>> ??? ??? y = y+65535
>>>
>>> ??? if(@2=="debugon")
>>> ??? {
>>> ??? ??? if(y==0 && @cast($vq, "vring_virtqueue")->vq->callback ==
>>> callback_addr)
>>> ??? ??? {
>>> ??? ??? ??? netrxfreecount[y] <<< gettimeofday_s()
>>>
>>> ??? ??? ??? pri...
2019 Jul 23
2
[PATCH] virtio-net: parameterize min ring num_free for virtio receive
...gt; (@cast($vq, "vring_virtqueue")->vring->used->idx) ---> we use this one
>>> to verify if we run out of free buffer in avail ring
>>> ??? if (y<0 && (y+65535)<4096)
>>> ??? ??? y = y+65535
>>>
>>> ??? if(@2=="debugon")
>>> ??? {
>>> ??? ??? if(y==0 && @cast($vq, "vring_virtqueue")->vq->callback ==
>>> callback_addr)
>>> ??? ??? {
>>> ??? ??? ??? netrxfreecount[y] <<< gettimeofday_s()
>>>
>>> ??? ??? ??? pri...
2019 Jul 19
1
[PATCH] virtio-net: parameterize min ring num_free for virtio receive
...ue")->vring->avail->idx)-
> (@cast($vq, "vring_virtqueue")->vring->used->idx) ---> we use this one
> to verify if we run out of free buffer in avail ring
> ??? if (y<0 && (y+65535)<4096)
> ??? ??? y = y+65535
>
> ??? if(@2=="debugon")
> ??? {
> ??? ??? if(y==0 && @cast($vq, "vring_virtqueue")->vq->callback ==
> callback_addr)
> ??? ??? {
> ??? ??? ??? netrxfreecount[y] <<< gettimeofday_s()
>
> ??? ??? ??? printf("no avail ring left seen, printing most recent 5
&...
2009 Jan 21
3
[LLVMdev] Load from abs address generated bad code on LLVM 2.4
Chris Lattner wrote:
> On Jan 20, 2009, at 2:10 AM, Andrew Haley wrote:
>
>> Chris Lattner wrote:
>>> On Jan 19, 2009, at 7:55 AM, Andrew Haley wrote:
>>>
>>>> This is x86_64. I have a problem where an absolute memory load
>>>> The current LLVM trunk does not have this bug. This seems quite a
>>>> nasty
>>>> bug; is
2019 Jul 19
0
[PATCH] virtio-net: parameterize min ring num_free for virtio receive
...>idx)-
> > (@cast($vq, "vring_virtqueue")->vring->used->idx) ---> we use this one
> > to verify if we run out of free buffer in avail ring
> > ??? if (y<0 && (y+65535)<4096)
> > ??? ??? y = y+65535
> >
> > ??? if(@2=="debugon")
> > ??? {
> > ??? ??? if(y==0 && @cast($vq, "vring_virtqueue")->vq->callback ==
> > callback_addr)
> > ??? ??? {
> > ??? ??? ??? netrxfreecount[y] <<< gettimeofday_s()
> >
> > ??? ??? ??? printf("no avail ring l...
2019 Aug 13
0
[PATCH] virtio-net: parameterize min ring num_free for virtio receive
...ng_virtqueue")->vring->used->idx) ---> we use this one
> >>> to verify if we run out of free buffer in avail ring
> >>> ??? if (y<0 && (y+65535)<4096)
> >>> ??? ??? y = y+65535
> >>>
> >>> ??? if(@2=="debugon")
> >>> ??? {
> >>> ??? ??? if(y==0 && @cast($vq, "vring_virtqueue")->vq->callback ==
> >>> callback_addr)
> >>> ??? ??? {
> >>> ??? ??? ??? netrxfreecount[y] <<< gettimeofday_s()
> >>>...